-
Notifications
You must be signed in to change notification settings - Fork 565
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NewAuthConfigurationsFromDockerCfg returns empty auth for macOS with docker desktop version 2.2.0.4 #827
Comments
Hi @linggao, thanks for reporting and sorry for the delayed response. This is likely related to #677. If you're using the osxkeychain with Docker for Mac, go-dockerclient isn't capable of loading credentials from the keychain. See some info in #677. I'd be willing to take a PR that enables that if CGO is enabled and if building on MacOS, but we still need to be able to build on other OSes and on MacOS with CGO disabled. |
@fsouza thanks for the response. I think the problem is that with docker desktop version 2.2.0.4 and above, there is a file called ~/.docker/plaintext-passwords.json shipped with it. After we uncheck "Securely store Docker logins in macOS keychain", the file is still there. After we did |
What we are doing now to temporarily fix it is: |
@linggao gotcha, yeah we can fix the logic to do whatever the |
@fsouza thanks for fixing it. Could you please put it in a tagged version so that we can pull it into our dependencies. We cannot point to the master because we need to get a stable version to test with. Currently we are point to v1.6.4. |
I upgraded docker on my MacBook to desktop version: 2.2.0.4 (43472). I unchecked "Securely store Docker logins to macOS keychain". I did
docker login ...
on terminal window, my auth is saved in ~/.docker/config.json file after the command. However, calling NewAuthConfigurationsFromDockerCfg returned empty auths. It seems that the code is looking for ~/.docker/plaintext-passwords.json file instead of ~/.docker/config.json. I do have this file after the docker upgrade, but it has the following content.The following is the output for docker version command.
The text was updated successfully, but these errors were encountered: