Docker Community Forums

Share and learn in the Docker community.

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


(Dionachris) #1

Hi all,

Newbie question here but I can’t figure out why I can’t push my image to the docker hub :frowning:

Steps taken;

  1. Account created with the docker hub (dionachris is my username)
  2. Public repository created with my account (dmvisits)
  3. Logged in with my user name using “sudo docker login”
  4. Image created using dockerfile (from CentOS6 base) created as dionachris/dmvisits
  5. I try to push the image up to the repository and it fails…

[diona@localhost ~]$ sudo docker push dionachris/dmvisits

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

I’m sure it’s something simple I’m doing wrong, but can’t for the life of me figure out what it is.

Any help greatly appreciated!

Thanks,

Chris


(Sabin Basyal) #2

What version of Docker are you running? Is it v1.6?


(Dionachris) #3

Client version: 1.5.0-dev
Client API version: 1.18
Go version (client): go1.3.3
Git commit (client): fc0329b/1.5.0
OS/Arch (client): linux/amd64
Server version: 1.5.0-dev
Server API version: 1.18
Go version (server): go1.3.3
Git commit (server): fc0329b/1.5.0
OS/Arch (server): linux/amd64


(Sébastien Santoro) #4

I can repro on CentOS 7, with Docker version 1.5.0-dev, build fc0329b/1.5.0 (the one in packages).

I then upgraded the server to use the virt7-testing CBS repository.

$ cat > /etc/yum.repos.d/CBS.repo
[virt7-testing]
name=virt7-testing
baseurl=http://cbs.centos.org/repos/virt7-testing/x86_64/os/
enabled=1
gpgcheck=0
^D

$ yum upgrade docker
[...]

$ docker --version
Docker version 1.6.0, build bdbc177

Source: Cloud page on the CentOS wiki.

@dionachris This page recommends EPEL for CentOS 6, but EPEL version is stilll 1.5.0, so you could consider to upgrade to CentOS 7 if you want to get along the rather rapid development cycle of Docker.


(Sean McLaughlin) #5

I’m having the same issue.


(Rkarakaya) #6

having the same issue:-(

FATA[0000] Repository does not exist: rkarakaya/test

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


(Mangled Deutz) #7

Hi,

People with docker version 1.5.0-dev - you are either using a development version built of master, or a modified docker.

If the former, please update to a stable/released version.
If the latter, then please turn to your distro (or whoever ships that modified docker).

Otherwise, let’s try to sort it out:

@rkarakaya I don’t see anything here: https://registry.hub.docker.com/u/rkarakaya/test/

Have you pushed something yet?


(Arnaud Castaner) #8

I have the same issue. I’m correctly logged on docker from the CLI. When trying to push to acastaner/website (https://registry.hub.docker.com/u/acastaner/website/) but docker tells me it doesn’t exist:

arnaud@ks37546:~/dev$ docker push acastaner/website
The push refers to a repository [acastaner/website] (len: 0)
FATA[0000] Repository does not exist: acastaner/website

I run docker 1.6 on Ubuntu 14.04:

arnaud@ks32346:~/dev$ docker version
Client version: 1.6.0
Client API version: 1.18
Go version (client): go1.4.2
Git commit (client): 4749651
OS/Arch (client): linux/amd64
Server version: 1.6.0
Server API version: 1.18
Go version (server): go1.4.2
Git commit (server): 4749651
OS/Arch (server): linux/amd64

(Arnaud Castaner) #9

I think I found the reason - minutes after I posted, of course :smile:
The name of the image didn’t match the repository - once I changed the name of the image, I managed to push. Maybe the error should be more clear?


(Rjapproves) #10

I ran into same issue but updated the repo as per the post and that fixed it. I did rebuild my image to match the repo name. So two things needed to happen to fix this.

Thanks
Rj


(Beetee2) #11

I’m having the same issue on Fedora21, and can’t seem to resolve it no matter what I do. There has to be something bigger going on here… Here is the message in my docker debug log:

sudo docker version (from Fedora 21 guest inside Windows 7 Host)

Client version: 1.6.0
Client API version: 1.18
Go version (client): go1.4.2
Git commit (client): 3eac457/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): 3eac457/1.6.0
OS/Arch (server): linux/amd64

sudo docker push - beetee2/personal-meteor

ERRO[2015] Handler for POST /images/{name:.}/push returned error: Error: Status 403 trying to push repository beetee2/meteor-personal to official registry: needs to be forced
ERRO[2015] HTTP Error: statusCode=403 Error: Status 403 trying to push repository beetee2/meteor-personal to official registry: needs to be forced
DEBU[2017] Calling POST /images/{name:.
}/push
INFO[2017] POST /v1.18/images/beetee2/meteor-personal/push?force=1&tag=
INFO[2017] +job push(beetee2/meteor-personal)
INFO[2017] +job resolve_repository(beetee2/meteor-personal)
INFO[2017] -job resolve_repository(beetee2/meteor-personal) = OK (0)
INFO[2017] Push of beetee2/meteor-personal to official registry has been forced
DEBU[2017] pinging registry endpoint https:/ /index.docker.io/v1/
DEBU[2017] attempting v1 ping for registry endpoint https:/ /index.docker.io/v1/
Repository does not exist: docker.io/beetee2/meteor-personal
INFO[2017] -job push(beetee2/meteor-personal) = ERR (1)

sudo docker push -f beetee2/personal-meteor

DEBU[1964] Calling POST /images/{name:.*}/push
INFO[1964] POST /v1.18/images/beetee2/meteor-personal/push?force=1&tag=
INFO[1964] +job push(beetee2/meteor-personal)
INFO[1964] +job resolve_repository(beetee2/meteor-personal)
INFO[1964] -job resolve_repository(beetee2/meteor-personal) = OK (0)
INFO[1964] Push of beetee2/meteor-personal to official registry has been forced
DEBU[1964] pinging registry endpoint https:/ /index.docker.io/v1/
DEBU[1964] attempting v1 ping for registry endpoint https:/ /index.docker.io/v1/
Repository does not exist: docker.io/beetee2/meteor-personal
INFO[1964] -job push(beetee2/meteor-personal) = ERR (1)

I’ve updated my fedora installation which included my linux headers. I’ve uninstalled and re-installed docker. I’ve tried keeping beetee2/meteor-personal ADDED to my DockerHub, and tried REMOVING it from my DockerHub, then pushing. I’ve tried sudo rm -rf /var/lib/docker/devicemapper. I’ve tried running the docker daemon with --dns specified (I use OpenDNS). I’ve tried disabling DNS.

None of it has worked obviously.

I’d greatly appreciate any tips in fixing this issue.

Yes I manually put the space in between http:/ / because “new users can’t post more than 2 links in a post”.


(Beetee2) #12

I sidestepped this issue by creating an ubuntu vm on Digital Ocean, ssh-ing in and cloning my git repo, vim-ing the files that need changed, installing docker, and pushing the image to DockerHub from that machine. So I’m not sure if it was a firewall issue or exactly what the problem was.


(Jason Al-Mansor) #13

I’m seeing this same issue as well, though I’m using overlay instead of device-mapper.


(Steven Pousty) #14

Same issue here with Fedora 21. I too tried first without a repo in dockerhub, then after creating an empty repo in dockerhub, then deleting it and trying again. All with the same errors. I can pull things from docker.io/fedora/* no problem so I don’t think this is a DNS issue.

$ sudo docker images
REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE
thesteve0/openshift-qpid latest 4ff0b3679c09 2 minutes ago 607.1 MB

$ sudo docker push thesteve0/openshift-qpid:latest
Do you really want to push to public registry? [Y/n]: Y
The push refers to a repository [docker.io/thesteve0/openshift-qpid] (len: 1)
FATA[0001] Repository does not exist: docker.io/thesteve0/openshift-qpid

$ sudo docker -v
Docker version 1.6.0, build 3eac457/1.6.0


(Steven Pousty) #15

Confirming that this DOES work on Fedora 20 with docker 15. Also a co-worker has confirmed this works with Docker 16 on Ubuntu. So my guess is that this is a fedora issue. I am going to move it over to them.


(Steven Pousty) #16

Work around on Fedora 21 with docker 16 is to use the following syntax:

sudo docker push docker.io/thesteve0/openshift-qpid:latest


(Jason Al-Mansor) #18

Looks like there’s an updated package in the f21 updates-testing repo that resolves this issue.


(Ageorge) #19

I did a yum update today and was upgrader to 1.6. Same problem as everyone else.

How do I get the fix you mentioned, Jason?

Thansk


(Jason Al-Mansor) #20

yum install --enablerepo=updates-testing docker-io

The package currently out there is docker-io-1.6.0-4.git350a636.fc21.x86_64


(Ageorge) #21

Lovely. Thanks, Jason.