-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Proxy-Cache for official images isn't working #13733
Comments
Have you tried |
I have the same errors with exact the same harbor setup. When I use
I get a different error When I use the command like in the bug description I get the same error as in issue description. The used docker version is:
|
Yeah, indeed, that worked here @EdKingscote @fandujar. A related issue here, but for Transparent proxy is: Seems like NGINX rewrite suggestion for Transparent Proxy, should take into consideration this. |
@EdKingscote I tried, but got same error @alfsch
|
@fandujar and @EdKingscote: the problem is docker 20.10 see #13740 |
I ran in to the Content-Type header problem last night as well, but only on machines that all just happened to be internal, so I figured it was a quirk of HAProxy being our front-end before I had to call it a night. Thanks @alfsch for sharing the link to that new issue, as it turns out purely by chance all of our external hosts are using older docker engines than our internal ones - that saved me a good chunk of investigation time this morning! Hopefully it won't take too long for a fix to materialize somewhere. |
Tks for sharing and for the help @EdKingscote @alfsch . I will close this one then. |
Expected behavior and actual behavior:
Commands like
docker pull myharbor.mycompany.com/myproxycache/alpine:latest
would result in image pulledSteps to reproduce the problem:
Versions:
Please specify the versions of following systems.
Result from docker pull command:
docker pull myharbor.mycompany.com/dockerhub/alpine:latest Error response from daemon: unknown: repository dockerhub/alpine not found
The text was updated successfully, but these errors were encountered: