-
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
unauthorized pull after v2.3.0 upgrade #15178
Comments
@sixeIa Indeed this seems to describe the problem. |
I was able to hot-fix this for my setup by adding |
Hi, I am having the same issue I tried a bunch of workarounds but they didn't work. nginx.conf
default.conf
|
@sixeela hello, I've also met this problem under harbor version 2.9.6, it causes pullImageBackOff in my cluster, so i want to know how to solve it by kubernetes configurations becuase i can not mannually add |
I'm running Harbor 2.2.2 as Pull-Through Registry with a little modification:
nginx configuration is modified, so that the server on 8443 will respond to the registry name only (setting server_name), and adding another server configuration for the server_names
registry-1.docker.io quay.io k8s.gcr.io
for the /v2/ endpoint. In addition, the URI is rewritten withrewrite ^/v2/(.*) /v2/$host/$1 break;
, which redirects the upstream host requests to the local public registry projects. Added another connect proxy and redirect docker to it, and now docker will pull transparently through Harbor.This works with 2.2.2, but the new 2.3.0 will provoke an error when pulling from those proxied upstream registries:
Error response from daemon: unauthorized: authorize header needed to send HEAD to repository: authorize header needed to send HEAD to repository
. Only theproxy 401
is logged, nothing from core.What's going wrong here?
The text was updated successfully, but these errors were encountered: