Expiration date on multi-arch images

[Justin Downie]

When we were simply building images on a single arch we were setting the LABEL in the Dockerfile for dev images and everything was good to go. However, when we moved to support multi-arch images and pushing them to quay through a CI the auto-expiration date no longer seems to be working in the repository. If i pull each image and check the labels they are set correctly for each image. Is there a good way we can go about setting auto-expire in a multi-arch format?

[Daniel Messer]

Hi Justin,

are you seeing that auto-expiration isn't applied coming from a LABEL inside a child manifest to a multi-arch image pushed from yoru CI to Quay? Or is the expiration applied but not honored? As an example, we do have auto-expiry on multi-arch image in Clair's upstream image repository at https://quay.io/repository/projectquay/clair?tab=tags

Best,

Daniel

On Wed, Oct 18, 2023 at 3:52 PM Justin Downie <jdo...@redhat.com> wrote:

When we were simply building images on a single arch we were setting the LABEL in the Dockerfile for dev images and everything was good to go. However, when we moved to support multi-arch images and pushing them to quay through a CI the auto-expiration date no longer seems to be working in the repository. If i pull each image and check the labels they are set correctly for each image. Is there a good way we can go about setting auto-expire in a multi-arch format?

--
You received this message because you are subscribed to the Google Groups "quay-sig" group.
To unsubscribe from this group and stop receiving emails from it, send an email to quay-sig+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/quay-sig/2e727184-8d8e-4563-9bd7-35fd81d5f5e8n%40googlegroups.com.

--

Daniel Messer

Product Management

Red Hat OpenShift