When CE team release images to customers, we release an image building guide as well. The image build guide will guide customers to set up a build env (VM) based on the version of images. If the image is uc18, the build env will be bionic (18.04) which has u-i 1.x installed.
CE released uc18 images to a customer. The u-i 1.x is used to build uc18 images. The customer would like to use a new feature "--validation=enforce" which u-i 2.x starts to support. Unfortunately, the image built by u-i 2.x doesn't has the GPT backup header. And, the system fails to boot without the GPT backup header.
There are two workarounds:
1. Update gadget.yaml to increase the partition size
2. Increase the image size by u-i parameter (--image-size)
I would like to confirm if the missing GPT backup header is expected when rootfs structure size smaller than actual rootfs contents. If it's an issue, I would expect that it can be fixed on u-i 3 and imagecraft. I haven't tried u-i 3.x. Will try it and get back to you.
Hi Paul,
When CE team release images to customers, we release an image building guide as well. The image build guide will guide customers to set up a build env (VM) based on the version of images. If the image is uc18, the build env will be bionic (18.04) which has u-i 1.x installed.
CE released uc18 images to a customer. The u-i 1.x is used to build uc18 images. The customer would like to use a new feature "--validation= enforce" which u-i 2.x starts to support. Unfortunately, the image built by u-i 2.x doesn't has the GPT backup header. And, the system fails to boot without the GPT backup header.
There are two workarounds:
1. Update gadget.yaml to increase the partition size
2. Increase the image size by u-i parameter (--image-size)
I would like to confirm if the missing GPT backup header is expected when rootfs structure size smaller than actual rootfs contents. If it's an issue, I would expect that it can be fixed on u-i 3 and imagecraft. I haven't tried u-i 3.x. Will try it and get back to you.