Docker pushes AWS ECR private repo, unable to cope with invalid JSON

Question

I tried AWS ECR and clicked a new tag on our private repository.

it looks like this:

export DOCKER_REGISTRY=0123123123123.dkr.ecr.us-east-1.amazonaws.com export TAG=0.1 docker build -t vendor/app-name . `aws ecr get-login --region us-east-1`" # generates docker login docker tag vendor/app-name $DOCKER_REGISTRY/vendor/app-name:$TAG docker push $DOCKER_REGISTRY/vendor/app-name:$TAG 

The input works, the tag is created, and I see it with docker images , but the click fails with an error.

 The push refers to a repository [0123123123123.dkr.ecr.us-east-1.amazonaws.com/vendor/app-name] (len: 2) b1a1d76b9e52: Pushing [==================================================>] 32 B/32 B Error parsing HTTP response: unexpected end of JSON input: "" 

This may very well be the wrong configuration, but I cannot figure out how to get more output from it. The command does not have debug level parameters, there are no other logs, and I can not intercept network traffic, because it seems to be encrypted.

Answer 1

Go to the same problem. For me, ensuring that the IAM user that I clicked the same as the ecr:BatchCheckLayerAvailability permission cleared this.

I originally planned to have a push-only policy and did not realize that this permission is required for a successful push.