harbor
harbor copied to clipboard
Proxy Cache DockerHub download issues
Hi all,
Since a long time we notice a couple of issues with the Proxy Cache connection to DockerHub in our different Harbor environments (version: v2.5.0).
The issue, that sometimes images can't be pulled. When we take a look into the proxy.log
file, we can see following entries:
Nov 14 08:30:05 192.168.176.1 core[2301]: 2022-11-14T13:30:05Z [WARNING] [/server/middleware/repoproxy/proxy.go:143]: Artifact: dockerhub/prom/node-exporter:v1.4.0, digest: is not found in proxy cache, fetch it from remote repo
Nov 14 08:30:05 192.168.176.1 core[2301]: 2022-11-14T13:30:05Z [WARNING] [/server/middleware/repoproxy/proxy.go:143]: Artifact: dockerhub/bloomberg/goldpinger:v3.6.1, digest: is not found in proxy cache, fetch it from remote repo
Nov 14 08:30:05 192.168.176.1 proxy[2301]: 53.18.118.253 - "GET /v2/dockerhub/prom/node-exporter/manifests/sha256:4dc469c325388dee18dd0a9e53ea30194abed43abc6330d4ffd6d451727ba3e6 HTTP/1.1" 401 152 "-" "containerd/v1.6.8" 0.003 0.004 .
Nov 14 08:30:05 192.168.176.1 proxy[2301]: 53.18.118.247 - "GET /service/token?scope=repository%3Adockerhub%2Fbloomberg%2Fgoldpinger%3Apull&service=harbor-registry HTTP/1.1" 200 954 "-" "containerd/v1.6.8" 0.023 0.024 .
Nov 14 08:30:05 192.168.176.1 proxy[2301]: 53.18.118.240 - "HEAD /v2/dockerhub/prom/node-exporter/manifests/v1.4.0 HTTP/1.1" 200 0 "-" "containerd/v1.6.8" 0.411 0.408 .
The issue is not happening at the same time - it is random. Also we have checked the rate limit but we are not hitting our rate limit at the time of the issue.
Is this issue also related to #16429? How can we solve this issues?
Thank you in advance!
Alexander Barth ([email protected]) on behalf of Mercedes-Benz Tech Innovation GmbH, Provider Information
It seems that the proxy.log quite normal, I can't see any issue, could you describe your issue more detail, and upload the core.log when the proxy fail. If you dockerhub account is not rate limited, then it could not be the same issue with #16429.
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 open topics everyday - removing stale label.
Alexander Barth ([email protected]) on behalf of Mercedes-Benz Tech Innovation GmbH, Provider Information
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.
For us the issue is resolved hence I will close the issue.
Alexander Barth ([email protected]) on behalf of Mercedes-Benz Tech Innovation GmbH, Provider Information