I am trying to push my locally build docker image to my new AWS ECR address. Currently it has been pushed to Docker hub without any problem. But when I try to push it to ECR I am getting errors.

It is either use of closed network connection or simply EOF

and when I check my container address, there is no image submitted. Steps I did so far

1. I added AmazonEC2ContainerRegistryFullAccess to my IAM user and I also have the admin access
2. I have a ECR URL
3. I tried both wifi and hotspot.
4. I increased the timeout limit for docker to 10 mins.
5. aws ecr get-login-password --region us-east-1 .... command returns "login successful" What am I missing here?

I am trying to push my locally build docker image to my new AWS ECR address. Currently it has been pushed to Docker hub without any problem. But when I try to push it to ECR I am getting errors.

It is either use of closed network connection or simply EOF

and when I check my container address, there is no image submitted. Steps I did so far

1. I added AmazonEC2ContainerRegistryFullAccess to my IAM user and I also have the admin access
2. I have a ECR URL
3. I tried both wifi and hotspot.
4. I increased the timeout limit for docker to 10 mins.
5. aws ecr get-login-password --region us-east-1 .... command returns "login successful" What am I missing here?

• amazon-web-services
• docker
• amazon-ecr

• Does this answer help with your issue? – vht981230 Commented Feb 16 at 5:48

1 Answer 1

Layer already exists isn't an error message. It just let you know the docker image layers already exist in the registry so there is no need to push it to again. Docker image has multiple layers so that when you update your new docker image with new version, it only pushes the changed layers instead of entire thing to improve time & space efficiency