Docker Community Forums

Share and learn in the Docker community.

Push error "FATA[0025] Error pushing to registry: Authentication is required."


(Moonsyim) #1

Would you please give me some idea how to fix ?
I have seen 2 similar issues here but it looks it is not fixed yet.

docker push moonsyim/amazon-linux-ami-tomcat-20150630:0.5

The push refers to a repository [moonsyim/amazon-linux-ami-tomcat-20150630] (len: 1)
ca729e775e1f: Image push failed

Please login prior to push:
Username (moonsyim):
WARNING: login credentials saved in /root/.dockercfg.
Login Succeeded
The push refers to a repository [moonsyim/amazon-linux-ami-tomcat-20150630] (len: 1)
ca729e775e1f: Image push failed
FATA[0025] Error pushing to registry: Authentication is required.


(Moonsyim) #2

docker version

Client version: 1.6.2
Client API version: 1.18
Go version (client): go1.3.3
Git commit (client): 7c8fca2/1.6.2
OS/Arch (client): linux/amd64
Server version: 1.6.2
Server API version: 1.18
Go version (server): go1.3.3
Git commit (server): 7c8fca2/1.6.2
OS/Arch (server): linux/amd64


(Moonsyim) #3

sorry to bother you,
my solution was

upgrade docker account - free to Micro
docker logout
docker login
after that try again, now it works.


(Sabin Basyal) #4

Thanks for the update. However, did your solution work before we manually cleared your cache?

Usually customers do not get caching issues. But for the ones who encounter this issue, either they need to wait for sometime or ask us to clear their cache.
Also, there is no need to upgrade to Micro. You had private repos thats why you needed one.

Cheers,
Sabin


(Love Nyberg) #5

I have the exactly same issue.

root@dockyard04:/var/jenkins/workspace/image-memcached/images/memcached# docker push 

bloglovin/memcached:2ba28da937a24598e3701d22ca6714988302aa04
The push refers to a repository [bloglovin/memcached] (len: 1)
5879a751fa63: Image push failed 

Please login prior to push:
Username (bloglovinci): 
WARNING: login credentials saved in /home/love/.dockercfg.
Login Succeeded
The push refers to a repository [bloglovin/memcached] (len: 1)
5879a751fa63: Image push failed 
FATA[0007] Error pushing to registry: Authentication is required. 

@sbasyal could you please clear our cache?


(Sabin Basyal) #6

Hi @jacksoncage,

Your’s is not the same issue or caching issue. The user bloglovinci who is trying to push, just has the read access to the repository bloglovin/memcached, so he is not able to push.

Regards,
Sabin


(Love Nyberg) #7

Ah bummer, thanks @sbasyal!


(Kitarp) #8

Hi,

I seem to be having the same issue-

sudo docker push kitarp/docker-pyspark-ipython:latest
The push refers to a repository [kitarp/docker-pyspark-ipython] (len: 1)
9db88ad02385: Image push failed

Please login prior to push:
Username (kitarp):
WARNING: login credentials saved in /home/pratik/.docker/config.json
Login Succeeded
The push refers to a repository [kitarp/docker-pyspark-ipython] (len: 1)
9db88ad02385: Image push failed
Error pushing to registry: Authentication is required.

Could you please clear my cache as well?

Thanks!


(Sabin Basyal) #9

@kitarp: You are not able to push because you are trying to push manually to an Automated Build.
kitarp / docker-pyspark-ipython is an Automated build, so you cannot push to it manually.

Regards,
Sabin


Pushing of image fails
(Kitarp) #10

@sbasyal - so if I were to uncheck the checkbox next to “Active” in automated builds, I would be able to push the image to this repo?


(Sabin Basyal) #11

@kitarp - That checkbox next to “Active” means if you would like to trigger the Automated build, when made changes in your code. Irrespective of that, you cannot push manually to the Automated Build Repository.


(Kitarp) #12

@sbasyal - where should I be pushing manually built images?


(Kitarp) #13

@sbasyal - thanks for your help. I deleted the existing repo, and created a new one which is not automated build based.


(Sabin Basyal) #14

@kitarp: Non-automated builds. The repository which is not set-up for Automated builds. When you click +Add Repository button, there are two options:

  1. Repository
  2. Automated Build
    You have to click on first one.

(Lorenzvth7) #15

@sbasyal Hi, I’ve a similar issue but I don’t get a real error code (FATA).

[root@ip-10-0-0-144 ~]# docker push 172.30.153.158:5000/openshift/busybox
The push refers to a repository [172.30.153.158:5000/openshift/busybox] (len: 1)
d7057cb02084: Image push failed 

Please login prior to push:
Username (test-admin): 
WARNING: login credentials saved in /root/.docker/config.json
Login Succeeded

The push refers to a repository [172.30.153.158:5000/openshift/busybox] (len: 1)
d7057cb02084: Image push failed 
Error pushing to registry: Authentication is required.

(Seanzyg) #16

I have the same issue.
docker version
Client version: 1.6.2
Client API version: 1.18
Go version (client): go1.5.1
Git commit (client): 7c8fca2
OS/Arch (client): linux/amd64
Server version: 1.6.2
Server API version: 1.18
Go version (server): go1.5.1
Git commit (server): 7c8fca2
OS/Arch (server): linux/amd64
the issue is below
root@sean:/home/sean# docker push seanzhao/ubuntu-django:14.04-django
The push refers to a repository [seanzhao/ubuntu-django] (len: 1)
2007f6be95ef: Image push failed

Please login prior to push:
Username (seanzyg):
WARNING: login credentials saved in /root/.dockercfg.
Login Succeeded
The push refers to a repository [seanzhao/ubuntu-django] (len: 1)
2007f6be95ef: Image push failed
FATA[0072] Error pushing to registry: Authentication is required.
what should i do?


(Sabin Basyal) #17

Hi,

You are not pushing to a right repository:
You should rather push to your account: docker push seanzyg/ubuntu-django:14.04-django

Your user-account is seanzyg and not seanzhao. I don’t even see any organization named seanzhao.

Regards,
Sabin