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

Cache Proxy organization fails to pull images from the RedHat registry

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • None
    • quay-v3.7.0
    • quay
    • False
    • False
    • Compatibility/Configuration, User Experience
    • Quay
    • Hide

      Create a new cache organization and for the Remote Registry use registry.redhat.io with credentials from a RedHat registry service account.

      or

      Create a new cache organization and for the Remote Registry use registry.access.redhat.com and provide no credentials

      Show
      Create a new cache organization and for the Remote Registry use registry.redhat.io with credentials from a RedHat registry service account. or Create a new cache organization and for the Remote Registry use registry.access.redhat.com and provide no credentials

      Cache proxy pulls fail in Quay 3.7 when targeting the upstream registries "registry.access.redhat.com" and "registry.redhat.io".

      During a pull using podman cli I receive the following error.

      Error: determining manifest type MIME type for docker://.../redhat_images/ubi7:latest reading manifeset sha256:.. received unexpected status: 500 Internal Server Error.

       

      The Quay pod logs have the following error.

      ManifestAlreadyExists: duplicate key value violates unique constraint "manifest_repository_id_digest"

        1. image-2022-05-11-10-49-30-492.png
          image-2022-05-11-10-49-30-492.png
          286 kB

              fmissi Flavian Missi
              rhn-gps-jperezes Jose Perez (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: