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
Comments
Try opening Keychain Access |
Well, it worked for me! What is the reasoning behind that? |
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 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) |
@99 feel free to close it then :) |
Removing "credsStore": "osxkeychain" from ~/.docker/config.json instead. |
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 |
I ran into this issue, and no matter amount unlocking/locking of the keychain, or deleting lines from Hope that helps someone in the future. Cheers! |
For those who are not on mac and/or changes with keychain did not helped. |
Hi,
I'm running command eval $(aws ecr get-login --region --no-include-email) and I'm receiving below error:
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
The text was updated successfully, but these errors were encountered: