Error with --email flag deprecation for `docker login`

In the 17.0.6 docker engine update, the -e and --email flags were deprecated. Sending the -e flag now results in a 400 error. The client should attempt to check the docker version or re-try without the email flag if it fails. This is a breaking change in the docker application, and should be fixed as soon as possible.

https://docs.docker.com/engine/deprecated/#-e-and---email-flags-on-docker-login

Originally encountered this issue with

$(aws ecr get-login)

This calls:

docker login -u AWS -p <TOKEN> -e none <ECR_URL>

[timwah]

I had the same issue until I realized that the tokens are base64 encoded - RTFM fail 😦.

session = boto3.Session()
ecr = session.client('ecr')
login = ecr.get_authorization_token()
b64token = login['authorizationData'][0]['authorizationToken'].encode('utf-8')
username, password = base64.b64decode(b64token).decode('utf-8').split(':')
registry = login['authorizationData'][0]['proxyEndpoint']

client = docker.from_env()
client.login(username, password, registry=registry)

[mrosales]

Sorry, shouldn’t have included the ecr bit in the issue. That was just how I was first made aware of the deprecation. I was collecting the URL and token from the ecr python sdk, and then using docker-py sdk to call docker login (not including an email field).

The code segment worked before upgrading to docker 17.0.6 yesterday, and then it stopped working. Calling the command line docker login with the token and URL from the python ECR command works fine.

This was the call I made. Using the same param values here in the command line worked fine, but failed in docker-py

docker.login(
                username="AWS",
                password=auth_data['authorizationToken'],
                registry=auth_data['proxyEndpoint']
               )

The error is:

docker.errors.APIError: 500 Server Error: Internal Server Error ("login attempt to https://<AWS_ID>.dkr.ecr.<REGION>.amazonaws.com/v2/ failed with status: 400 Bad Request")