Docker Push Error : FATA[0001] Respository does not exist

ageorge · May 4, 2015, 8:54pm

Installed it, restarted docker daemon and still get the same error.

jasonalmansor · May 4, 2015, 8:56pm

Could you paste the output of “docker version” and “docker info”?

ageorge · May 4, 2015, 8:59pm

Client version: 1.6.0
Client API version: 1.18
Go version (client): go1.4.2
Git commit (client): 350a636/1.6.0
OS/Arch (client): linux/amd64
Server version: 1.6.0
Server API version: 1.18
Go version (server): go1.4.2
Git commit (server): 350a636/1.6.0
OS/Arch (server): linux/amd64

Containers: 97
Images: 182
Storage Driver: devicemapper
Pool Name: docker-253:1-918119-pool
Pool Blocksize: 65.54 kB
Backing Filesystem: extfs
Data file: /dev/loop0
Metadata file: /dev/loop1
Data Space Used: 32.42 GB
Data Space Total: 107.4 GB
Data Space Available: 9.036 GB
Metadata Space Used: 34.31 MB
Metadata Space Total: 2.147 GB
Metadata Space Available: 2.113 GB
Udev Sync Supported: true
Data loop file: /var/lib/docker/devicemapper/devicemapper/data
Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
Library Version: 1.02.93 (2015-01-30)
Execution Driver: native-0.2
Kernel Version: 3.19.5-200.fc21.x86_64
Operating System: Fedora 21 (Twenty One)
CPUs: 4
Total Memory: 3.658 GiB
Name: ageorge
ID: CMEK:VPWF:3MDB:GWWS:PPAQ:OFRJ:UDD5:UFLY:QZPN:EXUP:Z5S2:CTTX
Username: ageorge
Registry: [https://index.docker.io/v1/]

sudo docker push apsd/wso2-am

Do you really want to push to public registry? [Y/n]: Y
The push refers to a repository [docker.io/apsd/wso2-am] (len: 0)
FATA[0002] Repository does not exist: docker.io/apsd/wso2-am

jasonalmansor · May 4, 2015, 9:01pm

Hmmm… it worked fine for me, though I’m using overlayfs instead of devicemapper. Not that I would expect that to make a difference.

looztra · May 5, 2015, 9:03am

Updated with the updates-testing package:

docker push ${login_name}/${image_name} fails
docker push docker.io/${login_name}/${image_name} fails

docker tag ${image_id} docker.io/${login_name}/${image_name} and then docker push docker.io/${login_name}/${image_name} is OK

└> docker version
Client version: 1.6.0
Client API version: 1.18
Go version (client): go1.4.2
Git commit (client): 350a636/1.6.0
OS/Arch (client): linux/amd64
Server version: 1.6.0
Server API version: 1.18
Go version (server): go1.4.2
Git commit (server): 350a636/1.6.0
OS/Arch (server): linux/amd64

└> docker info
Containers: 1
Images: 1017
Storage Driver: devicemapper
 Pool Name: docker-253:3-25304450-pool
 Pool Blocksize: 65.54 kB
 Backing Filesystem: extfs
 Data file: /dev/loop0
 Metadata file: /dev/loop1
 Data Space Used: 33.4 GB
 Data Space Total: 107.4 GB
 Data Space Available: 73.97 GB
 Metadata Space Used: 44.45 MB
 Metadata Space Total: 2.147 GB
 Metadata Space Available: 2.103 GB
 Udev Sync Supported: true
 Data loop file: /home/docker/devicemapper/devicemapper/data
 Metadata loop file: /home/docker/devicemapper/devicemapper/metadata
 Library Version: 1.02.93 (2015-01-30)
Execution Driver: native-0.2
Kernel Version: 3.19.5-200.fc21.x86_64
Operating System: Fedora 21 (Twenty One)
CPUs: 4
Total Memory: 15.62 GiB
Name: fedolooz.kalaari.net
ID: TMPI:T5I4:XRWA:UXE2:IQJK:RUWS:HTIZ:4MIR:TNUX:ZULS:G4R5:MZ6J
Username: looztra
Registry: [https://index.docker.io/v1/]

useltmann · May 5, 2015, 9:54am

this worked for me, thanks to @looztra for the hint:

docker tag <image-id> <repository>
docker push <repository>

specifying ‘docker.io’ is not necessary

find your image-id and repository by doing

docker images

jasonalmansor · May 5, 2015, 5:48pm

Just saw this…

http://pkgs.fedoraproject.org/cgit/docker-io.git/commit/?h=f21&id=fdc2897e9746d54d3fed7f13b4b827d8bba71be8

miminar · May 6, 2015, 6:35am

@jasonalmansor You’re right, that should fix your issues. docker-io-1.6.0-5.git350a636.fc21 is about to be pushed to updates-testing. You may want to subscribe to https://bugzilla.redhat.com/show_bug.cgi?id=1217987 so you get notified of its status change.

Please let me know if it doesn’t work for you.

bioothod · May 6, 2015, 2:20pm

docker-io-1.6.0-5.git350a636.fc21 works and pushes to repository, thank you, but it is extremely slow.

It takes several seconds with 100% CPU usage while ‘Buffering to disk’ and then several minutes actually pushing image upstream.

It was matter of minutes to push new image several releases ago, and not it takes more than hour and is not yet completed.

dgoradia · May 28, 2015, 8:42pm

This is still the case with Docker version 1.6.0, build 8aae715/1.6.0 on CentOS 7.

[root@localhost ~]# docker push dgoradia/insight-c7-base:latest

Do you really want to push to public registry? [y/n]: y
The push refers to a repository [docker.io/dgoradia/insight-c7-base] (len: 1)
FATA[0001] Repository does not exist: docker.io/dgoradia/insight-c7-base

[root@localhost ~]# docker push docker.io/dgoradia/insight-c7-base:latest

Do you really want to push to public registry? [y/n]: y
The push refers to a repository [docker.io/dgoradia/insight-c7-base] (len: 1)
FATA[0001] Repository does not exist: docker.io/dgoradia/insight-c7-base

[root@localhost ~]# docker version
Client version: 1.6.0
Client API version: 1.18
Go version (client): go1.4.2
Git commit (client): 8aae715/1.6.0
OS/Arch (client): linux/amd64
Server version: 1.6.0
Server API version: 1.18
Go version (server): go1.4.2
Git commit (server): 8aae715/1.6.0
OS/Arch (server): linux/amd64

[root@localhost ~]# docker info
Containers: 3
Images: 1
Storage Driver: devicemapper
 Pool Name: docker-253:1-33691187-pool
 Pool Blocksize: 65.54 kB
 Backing Filesystem: xfs
 Data file: /dev/loop0
 Metadata file: /dev/loop1
 Data Space Used: 578.7 MB
 Data Space Total: 107.4 GB
 Data Space Available: 16.9 GB
 Metadata Space Used: 1.028 MB
 Metadata Space Total: 2.147 GB
 Metadata Space Available: 2.146 GB
 Udev Sync Supported: true
 Data loop file: /var/lib/docker/devicemapper/devicemapper/data
 Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
 Library Version: 1.02.93-RHEL7 (2015-01-28)
Execution Driver: native-0.2
Kernel Version: 3.10.0-123.20.1.el7.x86_64
Operating System: CentOS Linux 7 (Core)
CPUs: 2
Total Memory: 3.69 GiB
Name: localhost.localdomain
ID: 76UB:XEOH:ZITT:VDGG:6JYY:MK2G:L6AW:SV5M:YLAV:5R57:3GFC:MW4A
Username: dgoradia
Registry: [https://index.docker.io/v1/]

sebiwi · May 29, 2015, 1:24pm

I have the same issue with CentOS 7.1.

Do you really want to push to public registry? [y/n]: y
The push refers to a repository [docker.io/sebiwi/jenkins] (len: 0)
FATA[0001] Repository does not exist: docker.io/sebiwi/jenkins

kizbitz · May 29, 2015, 8:22pm

I believe there is an issue with your binary. Could you replace it with our build and try again?

sudo systemctl stop docker
sudo mv /usr/bin/docker /usr/bin/docker.original
sudo curl https://get.docker.com/builds/Linux/x86_64/docker-latest -o /usr/bin/docker
sudo chmod +x /usr/bin/docker
sudo systemctl start docker

Thanks,

Jerry

fatherlinux · June 3, 2015, 3:19am

Yeah, there is definitely and issue with the Red Hat builds. Here is an example workaround which just worked for me. Basically, just do a fully qualified tag:

docker build -t fatherlinux/docker-bench-security .
docker tag fatherlinux/docker-bench-security docker.io/fatherlinux/docker-bench-security
docker push docker.io/fatherlinux/docker-bench-security

chixq · June 8, 2015, 6:21am

It works for me on CentOS 7.

Thank you.

eddy147 · June 13, 2015, 12:11pm

kizbitz:

I believe there is an issue with your binary. Could you replace it with our build and try again?
sudo systemctl stop docker
sudo mv /usr/bin/docker /usr/bin/docker.original
sudo curl https://get.docker.com/builds/Linux/x86_64/docker-latest -o /usr/bin/docker
sudo chmod +x /usr/bin/docker
sudo systemctl start docker
Thanks,

Jerry

This works for me. Thx @kizbitz for the answer.

beetree · June 16, 2015, 1:47pm

For me, works only if you specify docker.io in both tag and push.

sbasyal · June 16, 2015, 6:33pm

@beetree, you should remove your docker and replace it with the official docker installation. You may have to replace your docker binary if the installation is not available in your system.

jelmstrom · July 2, 2015, 8:08am

I’ve been experiencing the same problem with Debian (8.1) container, running on a centos7 host.
I’m running docker-in-docker on AWS so it might not be relevant to this case (in which case, tell me and I’ll create a fresh new topic ) …

My scenario is this:
Form my docker host (running Centos, docker version 1.6.2) I can build, tag, push and pull images from my private (corporate) repository on docker hub. But my Go build agents that are running on that host are not able to push to the repo.

I’ve installed docker.io 1.6.2 from jessie backports…

The error :

FATA[0000] Error response from daemon: Error: Status 403 trying to push repository {repo} to official registry: needs to be forced 


FATA[0000] Error response from daemon: Error: Status 403 trying to push repository docker.io/{repo} to official registry: needs to be forced

And of course, there is no ‘force’ option for push, at least not documented (?). Setting the * --confirm-def-push=false* flag in does not change the behaviour. Using the docker.io prefix workaround doesn’t make a difference in this case either.
I have started up a centos7 docker image and installed docker 1.6.2 on that and tried the same scenario - to try to isolate the condition. In that setup I can push which leads me to believe there is a problem with the jessie backports distribution, but I can be wrong…

Any ideas ?

Docker host setup

[root@ip-172-31-24-127 ~]# docker version 
Client version: 1.6.2
Client API version: 1.18
Go version (client): go1.4.2
Git commit (client): ba1f6c3/1.6.2
OS/Arch (client): linux/amd64
Server version: 1.6.2
Server API version: 1.18
Go version (server): go1.4.2
Git commit (server): ba1f6c3/1.6.2
OS/Arch (server): linux/amd64

[root@ip-172-31-24-127 ~]# docker info 
Containers: 15
Images: 154
Storage Driver: devicemapper
 Pool Name: docker-202:1-318767622-pool
 Pool Blocksize: 65.54 kB
 Backing Filesystem: xfs
 Data file: 
 Metadata file: 
 Data Space Used: 7.458 GB
 Data Space Total: 107.4 GB
 Data Space Available: 99.92 GB
 Metadata Space Used: 10.16 MB
 Metadata Space Total: 2.147 GB
 Metadata Space Available: 2.137 GB
 Udev Sync Supported: true
 Library Version: 1.02.93-RHEL7 (2015-01-28)
Execution Driver: native-0.2
Kernel Version: 3.10.0-123.8.1.el7.x86_64
Operating System: CentOS Linux 7 (Core)
CPUs: 2
Total Memory: 7.39 GiB
Name: ip-172-31-24-127.us-west-2.compute.internal
ID: TAE6:NVZ2:JXR4:U5GP:4A26:F6PT:N2OC:OJEW:E4AY:ZJ2V:HDH2:TEKT
Username: tradedoublergo
Registry: [https://index.docker.io/v1/]

Failing docker build agent setup


root@33cc40ed5ab9:/# docker version
Client version: 1.6.2
Client API version: 1.18
Go version (client): go1.3.3
Git commit (client): 7c8fca2
OS/Arch (client): linux/amd64
Server version: 1.6.2
Server API version: 1.18
Go version (server): go1.4.2
Git commit (server): ba1f6c3/1.6.2
OS/Arch (server): linux/amd64


root@33cc40ed5ab9:/# docker info
Containers: 15
Images: 154
Storage Driver: devicemapper
 Pool Name: docker-202:1-318767622-pool
 Pool Blocksize: 65.54 kB
 Backing Filesystem: xfs
 Data file: 
 Metadata file: 
 Data Space Used: 7.458 GB
 Data Space Total: 107.4 GB
 Data Space Available: 99.92 GB
 Metadata Space Used: 10.16 MB
 Metadata Space Total: 2.147 GB
 Metadata Space Available: 2.137 GB
 Udev Sync Supported: true
 Library Version: 1.02.93-RHEL7 (2015-01-28)
Execution Driver: native-0.2
Kernel Version: 3.10.0-123.8.1.el7.x86_64
Operating System: CentOS Linux 7 (Core)
CPUs: 2
Total Memory: 7.39 GiB
Name: ip-172-31-24-127.us-west-2.compute.internal
ID: TAE6:NVZ2:JXR4:U5GP:4A26:F6PT:N2OC:OJEW:E4AY:ZJ2V:HDH2:TEKT
Username: tradedoublergo
Registry: [https://index.docker.io/v1/]

Working centos 7 image

docker version
Client version: 1.6.2
Client API version: 1.18
Go version (client): go1.4.2
Git commit (client): ba1f6c3/1.6.2
OS/Arch (client): linux/amd64
Server version: 1.6.2
Server API version: 1.18
Go version (server): go1.4.2
Git commit (server): ba1f6c3/1.6.2
OS/Arch (server): linux/amd64

[centos@ip-172-31-24-127 ~]$ docker info
Containers: 15
Images: 154
Storage Driver: devicemapper
 Pool Name: docker-202:1-318767622-pool
 Pool Blocksize: 65.54 kB
 Backing Filesystem: xfs
 Data file: 
 Metadata file: 
 Data Space Used: 7.458 GB
 Data Space Total: 107.4 GB
 Data Space Available: 99.92 GB
 Metadata Space Used: 10.16 MB
 Metadata Space Total: 2.147 GB
 Metadata Space Available: 2.137 GB
 Udev Sync Supported: true
 Library Version: 1.02.93-RHEL7 (2015-01-28)
Execution Driver: native-0.2
Kernel Version: 3.10.0-123.8.1.el7.x86_64
Operating System: CentOS Linux 7 (Core)
CPUs: 2
Total Memory: 7.39 GiB
Name: ip-172-31-24-127.us-west-2.compute.internal
ID: TAE6:NVZ2:JXR4:U5GP:4A26:F6PT:N2OC:OJEW:E4AY:ZJ2V:HDH2:TEKT
Username: tradedoublergo
Registry: [https://index.docker.io/v1/]

darquewarrior · August 6, 2015, 12:37am

This worked for me. Once the name of the repo matched the name of my image I was able to push.

willa · August 18, 2015, 12:43pm

I am having the same issue running docker via Docker machine on OS X. docker info has the following output.

$ docker info
Containers: 2
Images: 132
Storage Driver: aufs
Root Dir: /mnt/sda1/var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 136
Dirperm1 Supported: true
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 4.0.9-boot2docker
Operating System: Boot2Docker 1.8.1 (TCL 6.3); master : 7f12e95 - Thu Aug 13 03:24:56 UTC 2015
CPUs: 8
Total Memory: 1.955 GiB
Name: default
ID: PZOX:YQGZ:4PAW:YT6F:56LM:RWIQ:V5WI:3NLL:Y6CH:RTMG:YBB7:3TVL
Debug mode (server): true
File Descriptors: 21
Goroutines: 36
System Time: 2015-08-18T12:29:58.174380168Z
EventsListeners: 0
Init SHA1:
Init Path: /usr/local/bin/docker
Docker Root Dir: /mnt/sda1/var/lib/docker
Username: willa
Registry: https://index.docker.io/v1/
Labels:
provider=virtualbox

docker login works just fine but when I try to push to an repo it doesn’t work. I have tried both

$ docker images
REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE
tomcat-openmrs197 latest 5a961ca87492 5 days ago 473.6 MB

docker push willa/tomcat-openmrs197:latest
The push refers to a repository [docker.io/willa/tomcat-openmrs197] (len: 1)
Repository does not exist: willa/tomcat-openmrs197

The fact that docker says the push refers to docker.io made suspect may be it is pointing to the wrong URL. So I decided to specify the repo explicitly as shown below without success. Why is docker refering to docker.io anyway? Is this normal?

docker push Docker
The push refers to a repository [Docker] (len: 1)
Repository does not exist: Docker

However I have created the repo on docker hub with the same name as seen here.

Note: I have direct access to the internet. No firewall or anything that would be interfering with this.

Thanks in advance.

Topic		Replies	Views
FATA[0000] Error pushing to registry: Tag does not exist Docker Hub	2	20863	July 9, 2015
FATA[0065] Error pushing to registry: Authentication is required Docker Hub	1	1622	July 12, 2015
FATA[0308] docker push Docker Hub	1	968	May 10, 2015
Docker push - FATA[0005] Error pushing to registry: Authentication is required Docker Hub	1	1717	July 10, 2015
FATA[0005] Error pushing to registry: Authentication is required Docker Hub	8	3737	June 18, 2015

Docker Push Error : FATA[0001] Respository does not exist

Docker host setup

Failing docker build agent setup

Working centos 7 image

Related topics