docker login doesn't work on macOS High Sierra

[NeilMenne]

Expected behavior

docker login completes

Actual behavior

error getting credentials - err: signal: segmentation fault, out: ``

Information

Diagnostic ID: CBB68278-7E6B-47E8-A48D-D265B0DB1052

Steps to reproduce the behavior

1. upgrade to macos high sierra
2. docker login (I am attempting to setup docker credentials for AWS like eval "$(aws ecr get-login --region us-east-1| sed -e 's/-e none//g')")

[guillaumerose]

Does it use custom client certificates (located in ~/.docker/certs.d) ?

[NeilMenne]

No, it doesn't. It creates a docker login command like docker login -u AWS -p ....

[mowreyw]

I am seeing the same issue. Login using eval $(aws ecr get-login) has been broken since moving to macOS High Sierra. A login command with temporary password is generated, but fails with exit status 1 , out: The user name or passphrase you entered is not correct

[FrenchBen]

The issue here is the lack of update from the AWS CLI, more than likely due to the fact that they run an older version of Docker in their offering.
This has been documented as a deprecated command for a while (1.11.0) and removed in 17.06, see:
https://docs.docker.com/engine/deprecated/#-e-and---email-flags-on-docker-login

There have been a couple of reports of it here:
aws/aws-cli#2753

The solution is to add --no-include-email to your eval.
eval $(aws ecr get-login --region us-east-1 --no-include-email)

[NeilMenne]

@FrenchBen, that fixes it for me. Thanks for finding that information; I spent a bit of time looking for relevant information to no avail.

Feel free to close.

[mowreyw]

My issue was something different, as I was already using --no-include-email. I found a line in ~/.docker/config.json that identified docker-credential-osxkeychain as the credentials store. Deleting this line allowed me to login using $(aws ecr get-login --region us-east-2 --no-include-email) once again.

[NeilMenne]

Sounds like we both made it out alive

[FrenchBen]

Closing as resolved for both parties

[jimmytuc]

It's work! Thanks

[docker-robott]

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked