New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MCR proxy cache does not remember pulled tags #15591
Comments
Yes, The behavior of Docker 20.10.x client changed, there is a local cache store the tag and digest, the |
@stonezdj thank you for this explanation. What solution do you see then to avoid this issue ? |
@stonezdj this issue is quite disturbing for some of our production images, did you have the chance to think about a potential solution please ? |
Noticed this behavior today too. dotnet/aspnet:6.0.0 is not listed even though it is pulled through proxy-cache. |
Still happen with |
I found it's deleted by
Note I pulled docker.io/library/busybox:latest at |
And this as well
|
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 |
More feedback: for some reason, the artifact has incorrect
Which makes |
Okay, my issue is actually #16230, however the artifact has a empty |
We are replicating our proxy-cached images to different clusters, but right now the tag is not replicated as only the digest exists in proxy-cache project. So we can not fetch images from replicated projects in other places due to this issue. |
I think one workaround is to allowing replication to proxy-cache projects. (related to what is describe in #15155, but instead of skipping those tags (#16286), allowing to replicate the blobs somehow (for better caching). Right now push to proxy-cached project is denined, but maybe having an option to allow this in project settings is useful for such scenarios. |
Happens to me too but with hub.docker.com images. Looks like it's indeed limited to images that are pulled through |
Looking at nginx logs, the only difference I see is that for some reason for nginx
bitnami/nginx
Looks like this is due to multiarchitecture images. Requesting UPDATE |
Found another interesting case. If you pull multiarch image that Harbor never seen before for some reason it triggers some routine that periodically logs
If I then remove that image and pull it again this no longer happens and image tag never appears. |
If anyone intersted, I found a workaround that fixes the issue completely. Comment out this line and rebuild harbor-core. harbor/src/pkg/registry/client.go Line 54 in 98e1b82
Ideally we would add small check here to ensure that harbor/src/pkg/registry/client.go Line 262 in 98e1b82
This tells remote registry that Harbor doesn't support |
This issue is being marked stale due to a period of inactivity. If this issue is still relevant, please comment or remove the stale label. Otherwise, this issue will close in 30 days. |
This issue was closed because it has been stalled for 30 days with no activity. If this issue is still relevant, please re-open a new issue. |
Still relevant. @stonezdj could you please reopen this issue? |
@stonezdj is it possible to reopen this issue please ? And to get information about the potential fix ? |
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 pull
something via Docker Hub proxydocker pull
something via MCR proxy/v2/.../tags/list
and/v2.0/.../artifacts/.../tags
also return no tags.Versions:
The text was updated successfully, but these errors were encountered: