The same (?) problem affects the xenial32 image. I assume the creation process is related (but I can open a new bug for this if not).
The same (?) problem affects the xenial32 image. I assume the creation process is related (but I can open a new bug for this if not).