Uploaded image for project: 'Project Quay'
  1. Project Quay
  2. PROJQUAY-4515

Expiry label should be applied to all linked images

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Normal
    • None
    • None
    • quay, quay.io
    • False
    • False
    • Quay Enterprise
    • Undefined
    • Hide

      I got a customer who is experiencing the same issue.
      Here is what customer said:
      ~~~
      Repository Tags: https://quay.io/repository/bitski/gettext?tab=tags
      Expected: sha-df167dc and pr-1 have the same expiration.
      Actual: only tag pr-1 has an expiration and sha-df167dc has got never
      ~~~

      Show
      I got a customer who is experiencing the same issue. Here is what customer said: ~~~ Repository Tags: https://quay.io/repository/bitski/gettext?tab=tags Expected: sha-df167dc and pr-1 have the same expiration. Actual: only tag pr-1 has an expiration and sha-df167dc has got never ~~~
    • 0

    Description

      The 'quay.expires-after=x' Dockerfile LABEL currently works only on the 1st image pushed to the registry. Id does not work images linked to the first image (for example, you retag the image and then repush, the expiration will not be set). This is a problem, the expiration time should be set for all images that have the flag in the Dockerfile.

      Zendesk ticket: https://coreos.zendesk.com/agent/tickets/18992

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. PROJQUAY-1713 Expiry label should be applied to all linked images

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. PROJQUAY-279 quay.expires-after ignored when pushing manifest with only existing layers

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Activity

            People

              sleesinc Kenny Lee Sin Cheong
              rhn-support-ibazulic Ivan Bazulic
              Dongbo Yan Dongbo Yan
              Votes:
              2 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated: