Closed wibed closed 7 months ago
this might not be related to the registry at all
https://github.com/rancher-sandbox/rancher-desktop/issues/6294
I think this is a registry issue...
Our registry just suddenly stopped working out of nowhere with the same errors you are facing above. Nothing in our helm chart has changed though... The registry had been working fine for 4-5 months now, but we are now getting 401s...
I've verified the htpasswd file has the correct user credentials, but any time that I attempt to docker login
or nerdctl login
to the registry it returns a 401 Unauthorized.
Edit: This ended up being incorrect SSL configuration on our side. The 401 was misleading...
docker info
values.yaml
verify
login via port-forward
% docker login -u flux 127.0.0.1:5000 Password: Error response from daemon: Get "http://127.0.0.1:5000/v2/": dial tcp 127.0.0.1:5000: connect: connection refused
exec -- echo $REGISTRY_AUTH_HTPASSWD_PATH
exec -- cat /auth/htpasswd
exec -- nc -w2 -z 0.0.0.0 5000 && echo true
% nc -w2 -z 127.0.0.1 5000 && echo true
% curl -vvv 127.0.0.1:5000/v2/
Trying 127.0.0.1:5000...
Connected to 127.0.0.1 (127.0.0.1) port 5000 (#0)
Connection #0 to host 127.0.0.1 left intact
why tho?