moby: Cannot provide multiple logins for the same docker registry

I wonder if anybody cares about this besides Gordon… 🙄

Interesting, that there seem to be not that much people facing this issue… I have had to work around this limitation quite often. So I wonder how we can get this rolling?

The whole “login” paradigm is… well… typical docker.

It should be possible to pass credentials to registry operations. With command line switches and/or environment variables.

Same problem here on GitLab. The only workaround is to create a service user with the exact set of permissions for each use case. It is very difficult to keep track of this service users and their permissions and since GitLab is pay-per-seat, this can get quite costly.

Same issue here, I am using Gitlab’s auto-build-image to build my project which use an image (as FROM) from another user container registry. the build.sh always overwrites the login to its own registry, so we can’t use images from another users as FROM. If we change CI_REGISTRY_USER CI_REGISTRY_PASSWORD, it’ll not push compiled image to its own registry. It’s frustrating.

Any news here?

Any news here?

I believe the fundamental problem is that docker ~/.docker/config.json "auths" is hostname+port based, not hostname+port+path based. so each login just overwrites the previous login to the same hostname+port.

It gets even worse with buildx.

E.g.: you have images in two repositories/namespaces of the same registry:

Without buildx I got around it like this:

docker login registry.example.com <with credentials for registryA>
docker pull registry.example.com/registryA/my-image
docker logout registry.example.com
docker login registry.example.com <with credentials for registryB>
docker tag registry.example.com/registryA/my-image registry.example.com/registryB/my-image
docker push registry.example.com/registryB/my-image

But if I try this with buildx imagetools, I get either ERROR: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed or ERROR: server message: insufficient_scope: authorization failed, because I cannot switch authentication between pull and push.

docker buildx imagetools create -t registry.example.com/registryB/my-image registry.example.com/registryA/my-image

One thing you can do is to create multiple configs and point docker to use the appropriate one for your commands. Was new to me as well, but docker supports a CLI argument to point it to the correct config dir:

docker --config $YOUR_SPECIALIZED_CONFIG_DIR <your actual docker command>

Hi, this ticket has a long time opened. Is it something that is not solved yet or simply someone forgot to close it?

I found two workarounds:

• Using Docker inside Docker
• Using a different config.json

And, I did not try it, but maybe it is also possible to use an alias in the host file (or DNS server) to have a different hostname for each registry.

My question is, is still necessary to use one of these workarounds, or has it been solved in any way?