harbor: MCR proxy cache does not remember pulled tags
Expected behavior and actual behavior: I have several proxies set up. Proxy for Docker Hub works as expected. However, Microsoft Container Registry proxy does not list tags which i have pulled.
Steps to reproduce the problem:
docker pullsomething via Docker Hub proxy- find this artifact in Harbor UI and see that there is a tag listed
docker pullsomething via MCR proxy- find this artifact in Harbor UI and see that there are no tags at all. API calls like
/v2/.../tags/listand/v2.0/.../artifacts/.../tagsalso return no tags.
Versions:
- harbor version: [2.3.2]
- docker engine version: [20.10.8]
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 2
- Comments: 20 (1 by maintainers)
Commits related to this issue
- Fix caching repository not remembering tags due to multiarch images. Fixes https://github.com/goharbor/harbor/issues/15591 — committed to creker/harbor by deleted user 2 years ago
Yes, The behavior of Docker 20.10.x client changed, there is a local cache store the tag and digest, the
docker pull <image>:<tag>might be changed to<image>@sha256:xxxxxx, it is converted to pull by digest, in this case, the Harbor proxy cache only get the request ofdocker pull <image>@sha256:xxxxxx, then it couldn’t create this tag in the proxy cache.Found default retention policy (see below) for proxy cache project doesn’t work as expected…
When dry-run, it’s trying to delete the artifact pulled 5 minutes ago tagged with
latest