[Bug 1998229] Re: Adding metadata file into OCI images
Cristovao Cordeiro
1998229 at bugs.launchpad.net
Wed Dec 14 16:19:00 UTC 2022
Thanks Brian. Samir is OOO so I'll cover the verification steps.
The test plan from this bug's summary is only applicable when this package is released into -
updates.
So here's my current test plan to verify the -proposed pocket:
1. git clone https://github.com/ubuntu-bartenders/ubuntu-old-fashioned
2. cd ubuntu-old-fashioned/scripts/ubuntu- bartender
3.
for SERIES in bionic focal jammy kinetic
do
./ubuntu-bartender --build-provider multipass \
--livecd-rootfs-repo https://git.launchpad.net/ubuntu/+source/livecd-rootfs \
--livecd-rootfs-branch ubuntu/$SERIES-proposed -- --project ubuntu-oci --series $SERIES
done
Each of the above bartender calls will produce a tarball with a different random name. Let's say
(for the sake of readability in this test plan) that those are "$SERIES-ubuntu-on-the-rocks.tar.gz":
4.
for SERIES in bionic focal jammy kinetic
do
mkdir $SERIES-build
tar -xf $SERIES-ubuntu-on-the-rocks.tar.gz -C $SERIES-build
sudo mount $SERIES-build/build.output/livecd.ubuntu-oci.ext4 /mnt
grep serial /mnt/etc/cloud/build. info
sudo umount /mnt
done
I've tested this, and I could see the /etc/cloud/build.info file (with the "serial" content) on
bionic, focal, jammy and kinetic.
This fixes the bug for me.
Thanks!
P.S> I don't think I have the right to "change the tag from verification-needed-bionic to verification-done-bionic".
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to livecd-rootfs in Ubuntu.
https://bugs.launchpad.net/bugs/1998229
Title:
Adding metadata file into OCI images
Status in livecd-rootfs package in Ubuntu:
Fix Released
Status in livecd-rootfs source package in Bionic:
Fix Committed
Status in livecd-rootfs source package in Focal:
Fix Committed
Status in livecd-rootfs source package in Jammy:
Fix Committed
Status in livecd-rootfs source package in Kinetic:
Fix Committed
Bug description:
[ Impact ]
* The existing Ubuntu container images are being built and published
without any metadata information. This will introduce a new cloud-like
path and metadata file, including the image's serial number within
(which is useful for users to pinpoint a specific revision of the image).
[ Test Plan ]
* Run (for any of the affected series):
$ docker run public.ecr.aws/ubuntu/ubuntu:jammy grep serial
/etc/cloud/build.info || echo "Image metadata not found"
* Currently, the output will be
grep: /etc/cloud/build.info: No such file or directory
Image metadata not found
* After the release, I'll trigger the Ubuntu container image
CI/CD pipelines, and re-run the Docker command from above.
* The output shall then be similar to:
serial: 20221125
[ Where problems could occur ]
Given that we're adding new content to the filesystem, there's little
room for regression. A potential pitfall could be the future introduction
of /etc/cloud/(...) into the minimal filesystem, which would then
potentially end up being altered.
[ Other Info ]
Here the PR I have made :
https://code.launchpad.net/~samirakarioh/livecd-rootfs/+git/livecd-rootfs/+merge/433431
https://code.launchpad.net/~samirakarioh/livecd-rootfs/+git/livecd-rootfs/+merge/433432
https://code.launchpad.net/~samirakarioh/livecd-rootfs/+git/livecd-rootfs/+merge/433433
https://code.launchpad.net/~samirakarioh/livecd-rootfs/+git/livecd-rootfs/+merge/433572
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1998229/+subscriptions
More information about the foundations-bugs
mailing list