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

404 when Clair trying to pull non-existant layers from quay.io S3

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • quay.io
    • False
    • None
    • False
    • 0

      Between 100 and 200 times per hour, quay submits manifests to Clair with layers that Clair can't pull down from S3. Clair encounters this error:

      failed to fetch layers: fetcher: encountered errors: error realizing layer sha256:...: fetcher: unexpected status code: 404 Not Found (body starts: \"<?xml version=\\\"1.0\\\" encoding=\\\"UTF-8\\\"?>\\n<Error><Code>NoSuchKey</Code><Message>The specified key does not exist.</Message><Key>sha256/ad/…</Key><RequestId>BGFSA40SFCMFYZMZ</RequestId><HostId>RpVd\
      

      It would be great if someone could investigate why this happens.

      Example manifest: 

      sha256:16e45bfea5118aabdee049a41283b9159686e510ec5d7fdeb66a6aa1cbcb2eb0
      

            Unassigned Unassigned
            jcroslan@redhat.com Joseph Crosland
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: