-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support <version>-immutable tagged stable images #23
Conversation
43cc927
to
44b3dbe
Compare
@edsantiago it's probably asking a lot, so PLMK if it's asking too much for you to review this. Esp. the "Simplify image-build automation scripts" commit is quite big since it prunes out a lot of legacy crap. I did perform a few runs of CI against just that commit, and they're happy. |
@TomSweeneyRedHat would you mind taking a look at the (short) README updates here, LMK if there are any major problems? |
@edsantiago NP at all if this is too much, I appreciate you're making an effort. |
The current and prior CI VMs contain cached copies of the latest Fedora container image for each arch. Unfortunately the last arch pulled is `arm64`, which results in it being the default image used by podman when `--arch` is not specified. Ensure this can never cause problems by hard-coding the `amd64` arch which will always match the VM. Signed-off-by: Chris Evich <cevich@redhat.com>
Signed-off-by: Chris Evich <cevich@redhat.com>
Signed-off-by: Chris Evich <cevich@redhat.com>
Couple doc changes for consideration or to be ignored. Your call. |
44b3dbe
to
485bc4c
Compare
Previously the `containers_build_push.sh` script was "installed" every time into the environment due to legacy architecture reasons. This is no-longer necessary, complex, confusing, and potentially fragile. Move the scripts under the `ci` directory and arrange for them to simply be run from there. Update tests, documentation, comments accordingly. Signed-off-by: Chris Evich <cevich@redhat.com>
There are circumstances where it's consequential to have image digests that change constantly. Add a "flavor" of podman/buildah/skopeo image with a unique tag, that's only ever pushed once. Update documentation. Signed-off-by: Chris Evich <cevich@redhat.com>
485bc4c
to
99c40a5
Compare
This is ready to go, letting it sit for a day or so in case there are last minute objections/feedback. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Note to me: Check next cron run and verify immutable images have been pushed. Send mail to podman list assuming images aren't overwritten on the subsequent cron run. |
Prior to containers/image_build#23 the automation using `build-push.sh` always pushed its images. This obscured a bug that occurs when `fqin_names` is an empty string in `get_manifest_tags()`. In this case, the `grep` command will exit non-zero, causing `push_images()` to: ``` die "Error retrieving set of manifest-list tags to push for '$FQIN'" ``` Fix this by adding an empty-string check and removing the unnecessary `grep`. Also, `push_images()` change `die "No FQIN(s) to be pushed."` into a warning, since the condition should not be considered fatal. Signed-off-by: Chris Evich <cevich@redhat.com>
Fixes: containers/automation_images#310
There are circumstances where it's consequential to have image digests
that change constantly. Add a "flavor" of podman/buildah/skopeo image
with a unique tag, that's only ever pushed once. Update documentation.