-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
docker.io proxy cache failing after V2.2 migration #14791
Comments
Just confirmed that this actually also affects repositories/images that worked before. Everything that is moving through docker.io proxy is getting always re-fetched Previous to finding this, we where using Version 2.1 (installed from respective helm chart) and it worked flawlessly |
Another problem i found, testing the pull of python:2.6 from the docker.io proxy i get:
This is a proxy cache. The artifact indeed does not exist visually on the Portal. I can also not see it in the DB (am i searching in the correct place?):
This is a proxy-cache that is public. If tag needs to be deleted it should be handled by the system. So, error returned is also misleading... |
@stonezdj Please have a look |
Related:
This seems like a concurrency problem? |
For me looks like caching works if I use |
using |
Same problem here on version 2.4.0 sometime images was cached, sometime never (on public or private repo)... |
Same issue on v 2.4.1 |
Same issue here, using 2.4.1. For me not limited to Library images. K8s Pull: Manual docker pull:
--> It is cached. For some reason some other images did get cached, i dont see the logic. |
Same issue on v2.5.0-98e1b82f |
1 similar comment
Same issue on v2.5.0-98e1b82f |
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 is still an issue. |
Same issue for me on |
Any news on this one? It's still an issue on v2.5. |
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. |
still an issue in v2.6.1 |
We also facing this issue in v2.6.1 |
Please specify the container images that fails to pull by proxy cache? |
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. |
Having this issue too
Confirmed the creds are correct. Even remade new creds. Same issue on three separate harbor registries. |
Ah it was a typo in the image. I wish the error was more clear. |
Summary of this issue: the image tag is not guaranteed to be cached in Harbor, because it depends on the docker client's behavior, if the tag/digest information is cached local, the docker client just sends a pull by digest request to the server, Harbor could not cache this image by tag, but cache it with digest. |
docker pulling some images through the proxy cache does not persist them.
Expected behavior and actual behavior:
Expected the images if they do not exist in proxy cache to be downloaded and persisted locally until deleted (by retain policy for example)
Steps to reproduce the problem:
Setup docker.io proxy cache on harbor registry and pull through it:
docker pull registry.foo.bar/docker.io/osixia/openldap:1.3.0
Versions:
Installed with harbor-helm
Additional context:
The text was updated successfully, but these errors were encountered: