Unable to auth with Docker Hub and private registries about docker-registry-proxy

[rpardini]

Hi @gokhansengun thanks for the report and sorry for taking so long to look at this.
I do use a few private registries with auth and its working (its the whole point of this).

The thing is those registries are not the official DockerHub, but simple private registries hosted by myself.

I don't have a private/paid DockerHub account to test with, and it seems that this problem only affects that specific use case: from the logs you posted, it seems like docker goes both to registry-1 as well as auth, both under .docker.io.

You could try adding some more hostnames to auth against, for example:

docker run --rm --name docker_registry_proxy -it \
       -p 0.0.0.0:3128:3128 \
       -v $(pwd)/docker_mirror_cache:/docker_mirror_cache \
       -v $(pwd)/docker_mirror_certs:/ca \
       -e REGISTRIES="k8s.gcr.io gcr.io quay.io" \
       -e AUTH_REGISTRIES="registry-1.docker.io:gsengun:THE_PASS auth.docker.io:gsengun:THE_PASS" \
       rpardini/docker-registry-proxy:latest

Could try that and post the logs again?

If that solves it, I could implement a way to avoid having to do it twice, or at least document that.

Thanks.

[manlme]

I met this problem too. it seems that token from auth.docker.io should not be cached or not valid for too long. it will expire and cause such problem.

[rpardini]

Interesting. I will investigate ASAP.

[outworlder]

I am having trouble authenticating to Quay, not entirely sure the issue is related. Quay doesn't redirect to other URLs, it only uses /v2 and /v2/auth

HIT [02/Nov/2018:18:50:16 +0000] "/v2/" 401 40 "HOST:quay.io" "PROXY-HOST:quay.io" "UPSTREAM:-"
HIT [02/Nov/2018:18:50:17 +0000] "/v2/auth" 200 1063 "HOST:quay.io" "PROXY-HOST:quay.io" "UPSTREAM:-"
MISS [02/Nov/2018:18:50:18 +0000] "/v2/<repository-redacted>/<image-name-redacted>/manifests/4.2.0-8" 401 40 "HOST:quay.io" "PROXY-HOST:quay.io" "UPSTREAM:50.16.237.72:443"

You'll see that /v2 is a HIT (401), /v2/auth is a HIT (200) (is it supposed to cache it?), but the image itself is a MISS (401).

Docker will say: Error response from daemon: unauthorized: authentication required

Authentication was configured:

Adding Auth for registry 'quay.io' with user '<redacted>'.

Pulling from public registries obviously works just fine, as does the caching.

[rpardini]

@outworlder I opened a separate issue #5 for this case. I've released 0.2.1 which could maybe help.
@gokhansengun and @manlme, 0.2.1 should fix DockerHub authentication issue. Please take a look at README.md for the instructions for DockerHub auth, please test and report back ;-)

[outworlder]

<Removed, commenting on the correct issue>