ECR get-login produces an invalid parameter for ECR get-login

[combusean]

I noticed this standard behavior using the aws ECR cli and found it unusual.

Anything I'm missing in this? This seems widespread.

$ aws ecr get-login
docker login -u AWS -p eyJw....= -e none https://....ecr.us-west-2.amazonaws.com

$(aws ecr get-login)
unknown shorthand flag: 'e' in -e
See 'docker login --help'.

Leaving out the -e in the docker command fixes this.

[combusean]

$ aws --version
aws-cli/1.16.55 Python/3.7.1 Darwin/18.0.0 botocore/1.12.45

[mnahkies]

See pull request #1922 - effectively the solution seems to be adding the --no-include-email parameter

[justnance]

@combusean - Thanks for reaching out. The '-e' option has been deprecated and is removed in docker version 17.06 and later. You must specify --no-include-email if you're using docker version 17.06 or later. The default behavior is to include the '-e' flag in the 'docker login' output. Basically, using the --no-include-email option will remove the -e flag from the output. Currently we are we are keeping the -e for backwards compatibility reasons as users may be using an old version of docker that still uses it.

Reference: #3669 and #3374

[no-response]

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.