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

quay.expires-after ignored when pushing manifest with only existing layers

XMLWordPrintable

    • 2
    • Hide

      Create sample Dockerfile

      # Dockerfile
      FROM scratch
      LABEL quay.expires-after=1h
      
      docker build -t some.quay.installation/debugrepo/str:willexpire .
      docker push some.quay.installation/debugrepo/str:willexpire
      
      docker tag some.quay.installation/debugrepo/str:willexpire some.quay.installation/debugrepo/str:willNOTexpire
      docker push some.quay.installation/debugrepo/str:willNOTexpire
      

      Navigate to the repository in Quay. Observe that willexpire picked up the label correctly, but willNOTexpire did not.

      Show
      Create sample Dockerfile # Dockerfile FROM scratch LABEL quay.expires-after=1h docker build -t some.quay.installation/debugrepo/str:willexpire . docker push some.quay.installation/debugrepo/str:willexpire docker tag some.quay.installation/debugrepo/str:willexpire some.quay.installation/debugrepo/str:willNOTexpire docker push some.quay.installation/debugrepo/str:willNOTexpire Navigate to the repository in Quay. Observe that willexpire picked up the label correctly, but willNOTexpire did not.

      In certain scenarios Quay ignores the quay.expires-after label, which I'm guessing has to do with no new layers being pushed. This can result in a situation where the same image has two different expiring states, even though their labels match and the GUI for expiring images has not been used:


      The screenshot is from a local Quay 3.2 installation.

      The expected behaviour would be that the new tag also honors the expiry label.

              Unassigned Unassigned
              stefan.breunig Stefan Breunig (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: