Cirrus: Multi-arch build auto-update + tagging update

This new VM image brings in two important updates to multi-arch
image build operations:

1. Future operational changes will no-longer require also updating VM
   images.  Updates to build-push made in `containers/automation_images`
   will automatically be picked up at runtime.
   ref: https://github.com/containers/automation_images/pull/123

2. On the next run, both `vX` and `vX.Y` tagged manifest-lists will be
   pushed.  This is now also reflected in the README.
   ref: https://github.com/containers/automation_images/pull/125

Signed-off-by: Chris Evich <cevich@redhat.com>
This commit is contained in:
Chris Evich
2022-04-07 13:27:22 -04:00
parent f838333b7e
commit a95f7f9ca1
2 changed files with 5 additions and 4 deletions

View File

@ -38,7 +38,7 @@ env:
UBUNTU_NAME: "ubuntu-2110"
# Google-cloud VM Images
IMAGE_SUFFIX: "c6464310661611520"
IMAGE_SUFFIX: "c4831699639992320"
FEDORA_CACHE_IMAGE_NAME: "fedora-${IMAGE_SUFFIX}"
PRIOR_FEDORA_CACHE_IMAGE_NAME: "prior-fedora-${IMAGE_SUFFIX}"
UBUNTU_CACHE_IMAGE_NAME: "ubuntu-${IMAGE_SUFFIX}"

View File

@ -18,9 +18,10 @@ The container images are:
* `quay.io/containers/podman:<version>` and `quay.io/podman/stable:<version>` -
These images are built daily. They are intended to contain an unchanging
and stable version of podman. Though for the most recent `<version>` tag,
image contents will be updated to incorporate (especially) security upgrades.
For build details, please [see the configuration file](stable/Dockerfile).
and stable version of podman. For the most recent `<version>` tags (`vX`,
`vX.Y`, and `vX.Y.Z`) the image contents will be updated daily to incorporate
(especially) security upgrades. For build details, please [see the
configuration file](stable/Dockerfile).
* `quay.io/containers/podman:latest` and `quay.io/podman/stable:latest` -
Built daily using the same Dockerfile as above. The Podman version
will remain the "latest" available in Fedora, however the other image