This is an issue affecting the Quay proxy cache feature.
When pulling an image from a proxy cache repository, Quay caches only the image layers requested by the client.
So for example, if one image layer is already stored locally, Quay will never request that image layer from the upstream registry and store it in the object storage.
This leads to some issues especially with Clair because it complains about missing image layers when attempting to scan a cached image.
Steps to reproduce the issue:
- Install Quay 3.10
- Set up Quay as a proxy cache repository for docker.io
- Pull 2 images that share some layers(example golang and python images:
$ podman pull <quay-registry-endpoint>/<cache-org-name>/golang:latest
$ podman pull <quay-registry-endpoint>/<cache-org-name>/python:latest
- Confirm python image is not scanned
- is related to
-
PROJQUAY-8428 Proxy-Cache - No storage found with uuid
-
- New
-
-
PROJQUAY-3873 Proxied layers sometimes not saved properly in cloud storage
-
- Closed
-