How to fix EOF error during docker push command

Question

I try to push an image in my public docker repository, but after some minutes I have this problem:

and during pushing, the following occurs many times (when retrying):

My version of docker is the following:

How to solve this problem ?

https://github.com/docker/distribution/issues/2349 @TarunLalwani — daniele3004, Jul 27 '17 at 10:48
Are you behind a proxy by any chance? If so, there are many different answers to help - including editing your proxy config. — tdensmore, Feb 07 '19 at 19:54

score 27 · Answer 1 · answered Mar 01 '22 at 02:21

27

When I push an image to ECR, an EOF error occured. The reason is remote repository[jdk-8-newrelic] does not exist. After creating the repository, PUSH succeeded.

answered Mar 01 '22 at 02:21

Ridox

1,073
13
18

2

This pointed me in the right direction: Terraform was creating the image repository with a different name from the one I was passing to `docker push`. – Paul Mar 04 '22 at 03:21
My issue was similar. I forgot to give myself permission to the repo. – Kyle May 16 '23 at 20:53

score 16 · Answer 2 · answered May 13 '22 at 20:35

16

I got this error when my image name was incorrectly formatted. I was trying to push an image called registry-url/my-repository/my-image-name:tag This is wrong; I need a repository per image name. registry-url/my-image-name:tag worked, once I created the repository named my-image-name.

This was on ECR.

answered May 13 '22 at 20:35

Jessitron

1,350
13
12

Why are you so confused with your answer, "once I created the repository named my-image-name." – optimus Jun 05 '22 at 12:36
3

This answer is helpful. It is not immediately obvious that "repository" means _everything except the tag_. – kbolino Mar 03 '23 at 18:26
`repository per image` - this line saved me. Thanks @Jessitron – Niranjan Aug 16 '23 at 06:58

score 10 · Answer 3 · answered Dec 05 '22 at 09:43

10

I was missing this policy AmazonEc2COntainerRegistryFullAccess in permission of the iam user

answered Dec 05 '22 at 09:43

Jose K J

121
1
6

score 5 · Answer 4 · edited Mar 11 '23 at 18:30

5

If you have profiles under ~/.aws/credentials (linux), you might need to specify profile name

aws ecr get-login-password  --profile <PROFILE-NAME>  | docker login --username AWS --password-stdin <ECR_NAME>.dkr.ecr.<REGION>.amazonaws.com

edited Mar 11 '23 at 18:30

Alijvhr

1,695
1
3
22

answered Mar 05 '23 at 10:58

oded rosianski

51
1
1

As it’s currently written, your answer is unclear. Please [edit] to add additional details that will help others understand how this addresses the question asked. You can find more information on how to write good answers [in the help center](/help/how-to-answer). – Community Mar 10 '23 at 12:41
This answer helped me figure out my problem, and that was because I have multiple AWS accounts for various environments and I was using the default one mistakenly when authenticating with ECR for docker login. Thanks. – Jonathan Kretzmer May 29 '23 at 13:30
Make you are connected to right profile with ECR access. – prayagupa Aug 29 '23 at 22:43

score 4 · Answer 5 · answered Oct 24 '22 at 04:56

In case you are trying to push into the AWS ECR, this happens when the connection to the repository has failed. This could be either because

the repository doesn't exist
the repository exists but in a different region
the AWS credentials are incorrect.
the AWS credentials have just been corrected

Once you have the repository created in the correct region and the AWS cli Credentials are corrected, ensure that you run the AWS docker login command once again and repeat the tag and push steps.

score 0 · Answer 6 · answered Mar 09 '20 at 06:30

I have met this issue nowadays when I am pushing an image to a private registry. And I checked out the Docker log and found that there was something unexpected about the proxy but I did not have to push to my private through the proxy. So I added my registry address to the Docker proxy whitelist to skip the proxy, and it worked. I wish it helps!

score 0 · Answer 7 · answered Jan 28 '22 at 15:09

I had a similar problem pushing to a private docker repository, and the problem was wrong credentials.

Try to read the logs:

Get-EventLog -LogName Application -Source Docker -After (Get-Date).AddMinutes(-5) | Sort-Object Time

ref: https://learn.microsoft.com/en-us/virtualization/windowscontainers/troubleshooting#finding-logs

score 0 · Answer 8 · answered Apr 07 '22 at 22:03

0

In my case, I had saved AWS credentials from another account where I did not have full access anymore. Check your C:\Users\YourUserName.aws\credentials if you are on Win.

answered Apr 07 '22 at 22:03

Anatoly Alekseev

2,011
24
27

score 0 · Answer 9 · answered Feb 21 '23 at 20:21

Yes, You need to create a repository in AWS ECR. PFB for AWS AC.

docker push aws-ac-id.dkr.ecr.us-west-2.amazonaws.com/build-agent:latest

Here I have created a build-agent ECR repository and the above command got successful. Don't forget to run the below command.

aws ecr get-login-password --region us-west-2 | docker login --username AWS --password-stdin aws-ac-id.dkr.ecr.us-west-2.amazonaws.com

How to fix EOF error during docker push command

9 Answers9