Skip to content
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

docker login doesn't work. Error message is "The user name or passphrase you entered is not correct." #3264

Closed
99 opened this issue Apr 13, 2018 · 9 comments
Labels
closing-soon This issue will automatically close in 4 days unless further comments are made.

Comments

@99
Copy link

99 commented Apr 13, 2018

Hi,

I'm running command eval $(aws ecr get-login --region --no-include-email) and I'm receiving below error:

WARNING! Using --password via the CLI is insecure. Use --password-stdin.
Error saving credentials: error storing credentials - err: exit status 1, out: `The user name or passphrase you entered is not correct.`

aws --version: aws-cli/1.14.60 Python/3.6.5 Darwin/17.4.0 botocore/1.9.13
docker --version: Docker version 18.03.0-ce, build 0520e24
MacOS High Sierra (10.13.3)

Would like to know why this error is occurring and how do I fix it? I tried to research here in aws docs, it but no luck

Thank you,
99

@dennislky
Copy link

Try opening Keychain Access
Right-click on the login keychain
Lock it and then unlock it again

@mfornasa
Copy link

Well, it worked for me! What is the reasoning behind that?

@JordonPhillips
Copy link
Member

Looks like there may be a bug in the osx keychain credential helper in docker on newer versions of osx: docker/docker-credential-helpers#65

Some have said that rebooting solves the problem. Some have said that removing that credential helper fixes it, though I would highly suggest trying other avenues before you do that.

It doesn't appear that this is a CLI issue though. If you find more info then let us know.

@JordonPhillips JordonPhillips added the closing-soon This issue will automatically close in 4 days unless further comments are made. label Apr 27, 2018
@99
Copy link
Author

99 commented Apr 27, 2018

@JordonPhillips made it work after reboots, restarts, reinstall, etc . Have no idea what fixed it. So not much here to share.( But I have 2 more co-workers who just got their new High Sierra laptops and hit the same problem)
I think we can close this ticket not much here

@dinamic
Copy link

dinamic commented Jun 12, 2018

@99 feel free to close it then :)

@99 99 closed this as completed Jun 12, 2018
@wahengchang
Copy link

wahengchang commented Oct 29, 2018

Removing "credsStore": "osxkeychain" from ~/.docker/config.json instead.

@rdonkin
Copy link

rdonkin commented Aug 7, 2020

Thanks @dennislky - your #3264 (comment) worked for me on macOS 10.13 with Docker 19.03.8. Simplest solution I've seen, tried various other options including editing ~/.docker/config.json

@jfortier-haptiq
Copy link

jfortier-haptiq commented Dec 5, 2020

I ran into this issue, and no matter amount unlocking/locking of the keychain, or deleting lines from ~/.docker/config.json worked for me. Apparently if you're using a terminal remotely (which I do between my macs) you need to run $ security unlock-keychain which is the equivalent of opening your keychain (but it works remotely). Helpful for anyone who runs into this issue and would like to script around it!

Hope that helps someone in the future. Cheers!

@punitpandey
Copy link

For those who are not on mac and/or changes with keychain did not helped.
Removing "credsStore" and "credHelpers" nodes from docker config file will do the magic. You can delete the .docker/config.json file as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closing-soon This issue will automatically close in 4 days unless further comments are made.
Projects
None yet
Development

No branches or pull requests

9 participants