Open drzero42 opened 5 years ago
I tried to push a Image to docker hub an it fails. Tested with sucessful img login
and -v $HOME/.docker:/root/.docker
running inside of a docker container. So build works, but push fails.
Successfully built docker.io/<REPO>/<IMAGE>:latest
Pushing docker.io/<REPO>/<IMAGE>...
server message: insufficient_scope: authorization failed
same here. Any info how to fix this?
Same problem here, can't pull image because of credential error :
img pull redis Pulling redis... rpc error: code = Unknown desc = error getting credentials - err: exit status 1, out: Exhausted all available authentication mechanisms (tried: EXTERNAL) (available: EXTERNAL)
So it's impossible to use this tool....
I was able to track down the Exhausted all available authentication mechanisms (tried: EXTERNAL) (available: EXTERNAL)
error down to the "credsStore": "secretservice"
setting in ~/.docker/config.json
. That message seems to be a D-Bus message telling that the application is not entitled to get secrets from the user's credential store. If I remove the credsStore setting and login again, the error is gone and everything works as expected.
I assume this is due to the fact that img re-executes itself and enters some namespace. When the re-execed process then tries to connect to the secret store, it does so with a different uid which is not allowed to access the passwords.
I have no idea how this could be fixed, although the workaround is to not use secretservice in conjunction with img.
I'm on Ubuntu 18.04 and have grabbed the img binary directly from github. When I run "img pull" or "img push" for any image, both Docker Hub and others, I get an error complaining about not being able to get credentials.
It works fine with Docker:
Is this a bug in img or something to do with my system?