Dockerhub authentication... again

[tinkerdudeno1]

I've scrolled through the closed issues and discovered that authentication against Dockerhub or private registries requires /root/.docker/config.json to be mounted. So I did:

• docker login on every node of my swarm
• Mount the aforementioned file into the container in the exact same location and make sure it's in the right place and readable
• Add the WITH_REGISTRY_AUTH=true environment variable to the service

but I still get the toomanyrequests error from Dockerhub. When I docker pull on the cli of my nodes, everything is fine. Shepherd, however, does not seem to get the authentication straight. The log says

Send registry authentication details to swarm agents,

immediately followed by:

toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit,

which only happens when I pull unauthenticated in my company.

Is there anything else I can try?

Thanks in advance!

[djmaze]

@tinkerdudeno1 Sorry for the late reply. I just built a clean solution. If you are working on amd64 machines, could you try out the test image at mazzolino/shepherd:pr-61? And then set REGISTRY_USER and REGISTRY_PASSWORD as documented here.

Does that work for you?

[krassdanke]

Hey, I had the same behavior but another error message (no crendetials at all).
When using mazzolino/shepherd:pr-61 and configuring REGISTRY_USER and REGISTRY_PASSWORD, it works.

Hope this helps!

[tinkerdudeno1]

Sorry for the late reply myself. I was off work and have meanwhile worked around this issue by deploying a registry serving as a proxy to Dockerhub. The registry itself was logged into Dockerhub so Shepherd was able to pull images from Dockerhub via this registry just fine. Interestingly, this worked, even though it also required authentication.

But: I can also confirm that pr-61 works just fine. IMHO, it's a step in the right direction as to new users it's more straight-forward to configure registry credentials via env variables rather than relying on the system login status.

So thanks for your effort!