Docker Community Forums

Share and learn in the Docker community.

Error pushing to registry: Authentication is required


(Ben Hamner) #1

I’m hitting an error with automated builds on Docker Hub that’s been regularly failing for the past day with the error

Error pushing to registry: Authentication is required.

Here’s an example of a failed build: https://registry.hub.docker.com/u/kaggle/r/build_id/53243/code/bvep6hoqrvyqyy69zmr2cx8/

Here’s other users hitting the same problem: https://github.com/docker/docker-registry/issues/997

The issue had occurred previously in issue 995 on the same repo.

Any ideas for a resolution?


(Jerry Baker) #2

We are currently having an issue with authentication on our end. Our operations team is currently working on the issue.

You can track the status at: http://status.docker.com/

Sorry for the inconvenience.

Jerry


(Ben Hamner) #3

Thanks @kizbitz! Looking forward to the fix


(Jerry Baker) #4

Hi Ben,

It turns out that the problem with your build is that your repository name is only one character. (You discovered a bug in our validation on the create form) You shouldn’t have been able to create a repository with a one character name. They’ve made changes to the code base recently so that’s why you just started getting the errors.

Unfortunately you’re going to have to create a new repository for that build. When you name it just make sure it has at least two characters. (The site mentions 3 characters, but I just confirmed with the dev team that they have a PR that fixes the validation and will switch the 3 to 2)

I apologize for the inconvenience,

Jerry


(Ben Hamner) #5

Thanks @kizbitz - that helps a lot!

We’ll do that, but is there any reason you’re blocking repos with single character names? We really like having kaggle/r, because the language R is just one character and fits nicely with the naming conventions we have with kaggle/python and kaggle/julia.

(As a side note, I noticed you’re in Indiana. There’s at least one more Docker user in Indiana - https://twitter.com/jeffmoser wrote most of the current version of kaggle.com & we’re big fans of Docker)


(Mohammad Naghavi) #6

I’m getting the same error for multi character repo name. I even tried to rename the repo but nothing changed. The status page shows all ok.


(Shaun Jackman) #7

I’m seeing this error as well:

https://registry.hub.docker.com/u/sjackman/linuxbrew-standalone/build_id/20501/code/bjeezdairfruvaaomwmfife/


(Mikkel Kroman) #8

Ditto:
https://registry.hub.docker.com/u/mkroman/inspircd/build_id/70619/code/bdqg9hhgkfzkpuiqwzj6evb/

Edit:
When trying to push an image I get the following:

The push refers to a repository [mkroman/inspircd] (len: 1)
dc56c396d33b: Image push failed 
FATA[0021] Error pushing to registry: Authentication is required.

(Darius Krištapavičius) #9

Same error here: https://registry.hub.docker.com/u/darneta/siwapp-sf1/builds_history/238575/ :frowning:


(Zjeraar) #10

Yep seeing this error too atm.


(Jorge Obiols) #11

I have te same error, With an automated build that was working fine for months, today i changed a little the Dockerfile and began to give this error "Error pushing to registry: Authentication is required."
I Delete and recreate the repo but no way
Is there any workaround???


(Darius Krištapavičius) #12

It was Docker issue ‘Docker push fails with “Error pushing to registry: Authentication is required”’ seems to be fixed now.
https://status.docker.com/pages/history/533c6539221ae15e3f000031


(Dbabits) #15

@kizbitz I got this error now (June 26) .“Error pushing to registry: Authentication is required”.
Build id bfubsgfkjo8gwgjqcpassy5
Docker team: why do you keep replying that the issue is fixed, when it’s clearly not fixed, or comes right back all the time?


(Rvydhya) #16

Hi

I am also getting the same error “Error pushing to registry: Authentication is required.”.Can you please let me know if it is fixed?


(Rvydhya) #17

Hi

this is now working thanks


(Aratto) #18

I seem to experience this right now:

...
1f80eb0f8128: Image push failed 

Please login prior to push:
Username (aratto): 
WARNING: login credentials saved in /home/andrea/.docker/config.json
Login Succeeded
The push refers to a repository [aratto/jenkins-swarm-slave] (len: 1)
93cad8499ae8: Image already exists 
...
1f80eb0f8128: Image push failed 
Error pushing to registry: Authentication is required.

(Denis Davydkov) #19

Hello!

Got the same issue:

   ....
   2e16500c0801: Image push failed

    Please login prior to push:
    Username (beenokle):
    WARNING: login credentials saved in /home/ubuntu/.docker/config.json
    Login Succeeded
    
    The push refers to a repository [....] (len: 2)
    2e16500c0801: Image push failed
    Error pushing to registry: Authentication is required.

(Anjunnikrishnan) #20

I got an error saying “Error pushing to registry: authentication required”!!
How do I fix this??


(Parrish) #21

I ran into this, but in my case it’s because the repository had originally been setup as an automated build. Even without automated builds enabled, it would reject pushes. Deleting and recreating the repo fixed it.


(Marvin Guerra) #22

I received the same error while following the tutorial which implies that

docker push [image]

should prompt you for your login info. Instead I ran:

docker login
docker push [image]

and that solved the issue for me