Description of problem: I can build and tag a docker image on my local machine but I can not push it to dockerhub. I am sure I have a dockerhub account and I can push with F20 and docker 15. Maceij can push with Ubuntu and Docker 16. Version-Release number of selected component (if applicable): Docker version 1.6.0, build 3eac457/1.6.0 How reproducible: Always Steps to Reproduce: 1. Make a local docker image 2. Tag it 3. Try to push it to dockerhub Actual results: $ sudo docker build -t thesteve0/openshift-qpid:latest . Sending build context to Docker daemon 2.048 kB Sending build context to Docker daemon Step 0 : FROM fedora/qpid ---> 6b45d8271e13 Step 1 : MAINTAINER spousty <spousty> ---> Using cache ---> 32b450b8f57a Step 2 : ENV IMAGE_DESCRIPTION QPID C++ AMQP Server 0.30.3 ---> Using cache ---> 03be2f186029 Step 3 : ENV IMAGE_TAGS qpid,qpid030, ---> Using cache ---> 13797654c23f Step 4 : ENV IMAGE_EXPOSE_SERVICES 5672:qpid ---> Using cache ---> 3a0843e1e66e Step 5 : EXPOSE 5672 ---> Using cache ---> 465c93d05637 Step 6 : ENTRYPOINT qpidd -t --auth=no ---> Using cache ---> 4ff0b3679c09 Successfully built 4ff0b3679c09 $ 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 Expected results: The image should be pushed to dockerhub Additional info:
See the thread starting here for this issue hitting another user a few days ago https://forums.docker.com/t/docker-push-error-fata-0001-respository-does-not-exist/1309/11
The current workaround: sudo docker push docker.io/thesteve0/openshift-qpid:latest. You need to include the docker.io/ prefix when pushing to the Hub.
I've noticed this issue as well. I tried swapping the package binary with the binary from docker and it worked fine and it didn't display the public registry prompt.
Thank you Steven for reporting this. PR https://github.com/rhatdan/docker/pull/48 fixes it.
docker-1.6.0-3.git9d26a07.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/docker-1.6.0-3.git9d26a07.fc22
docker-io-1.6.0-5.git350a636.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/docker-io-1.6.0-5.git350a636.fc21
docker-io-1.6.0-1.git350a636.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/docker-io-1.6.0-1.git350a636.fc20
Package docker-1.6.0-3.git9d26a07.fc22: * should fix your issue, * was pushed to the Fedora 22 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing docker-1.6.0-3.git9d26a07.fc22' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-7836/docker-1.6.0-3.git9d26a07.fc22 then log in and leave karma (feedback).
docker-1.6.0-3.git9d26a07.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
docker-io-1.6.2-1.git9f4bf0a.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/docker-io-1.6.2-1.git9f4bf0a.fc21
docker-io-1.6.2-3.gitc3ca5bb.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/docker-io-1.6.2-3.gitc3ca5bb.fc21
docker-io-1.6.2-3.gitc3ca5bb.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.