Actually I was not aware ubuntu-image 1.x was still used!
You probably already thought about that, but did you try ubuntu-image 3.X for this build? (maybe this is one of the builds using flash-kernel and you cannot use u-i 3 yet).
Since our current efforts are directed towards imagecraft, I doubt we will be able to invest time fixing ubuntu-image 2.X.
Anyway, an important thing to note in your gadget YAML where you define the structure of the image: The "size" key is more a "recommended/desired" value than a enforced one. This is handled by a snapd library so even with ubuntu-image 3.X you may encounter the same problem. But, recently a new "min-size" key was added in the VolumeStructure object, see [0]. I do not know for sure this could solve your problem, but using this and u-i 3.X could be worth a try.
Hey Ethan,
Actually I was not aware ubuntu-image 1.x was still used!
You probably already thought about that, but did you try ubuntu-image 3.X for this build? (maybe this is one of the builds using flash-kernel and you cannot use u-i 3 yet).
Since our current efforts are directed towards imagecraft, I doubt we will be able to invest time fixing ubuntu-image 2.X.
Anyway, an important thing to note in your gadget YAML where you define the structure of the image: The "size" key is more a "recommended/ desired" value than a enforced one. This is handled by a snapd library so even with ubuntu-image 3.X you may encounter the same problem. But, recently a new "min-size" key was added in the VolumeStructure object, see [0]. I do not know for sure this could solve your problem, but using this and u-i 3.X could be worth a try.
[0] https:/ /github. com/snapcore/ snapd/blob/ 08888455fa5da4f e078b2d57234aec 7f16d38d72/ gadget/ gadget. go#L279