RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1218639 - docker push to dockerhub does not work (docker 1.16)
Summary: docker push to dockerhub does not work (docker 1.16)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: docker
Version: 7.1
Hardware: All
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Michal Minar
QA Contact: Luwen Su
URL:
Whiteboard:
Depends On: 1217987
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-05-05 13:19 UTC by Michal Minar
Modified: 2019-03-06 01:32 UTC (History)
23 users (show)

Fixed In Version: docker-1.6.2-6.el7.x86_64
Doc Type: Bug Fix
Doc Text:
Cause: Docker did not try to match short names against local fully qualified images names while doing a push. Consequence: Push command reported that image name could not be found. User had to fully qualify the argument and run the push again. Fix: Docker now tries to match short names against local images fully qualified with default registry (those added with --add-registry flag). Result: User doesn't have to fully-qualify image name in order to push it to one of default registries.
Clone Of: 1217987
Environment:
Last Closed: 2015-06-23 09:29:30 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:1167 0 normal SHIPPED_LIVE docker bug fix update 2015-06-23 13:29:05 UTC

Description Michal Minar 2015-05-05 13:19:44 UTC 
+++ This bug was initially created as a clone of Bug #1217987 +++

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:

--- Additional comment from Steven Citron-Pousty on 2015-05-03 17:11:15 EDT ---

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

--- Additional comment from Andy Goldstein on 2015-05-03 22:14:23 EDT ---

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.

--- Additional comment from Jason Al-Mansor on 2015-05-04 11:39:52 EDT ---

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.

--- Additional comment from Michal Minar on 2015-05-05 07:24:17 EDT ---

Thank you Steven for reporting this. PR https://github.com/rhatdan/docker/pull/48 fixes it.
Comment 2 Michal Minar 2015-05-05 13:38:24 UTC 
PR for rhel7: https://github.com/rhatdan/docker/pull/49
Comment 3 Michal Minar 2015-05-29 08:13:14 UTC 
Although the PR has been merged, current rhel7-1.6 branch stays buggy. I'll resubmit the PR again.
Comment 4 Daniel Walsh 2015-06-02 18:11:37 UTC 
Michal can you verify this is fixed in docker-1.6.2 version.
Comment 5 Michal Minar 2015-06-03 06:39:39 UTC 
Yes, it's fixed.
Comment 7 Luwen Su 2015-06-15 07:57:25 UTC 
In docker-1.6.2-10.el7.x86_64

start daemon as #docker -d -D &
#docker push docker.io/timesu/busybox

INFO[0199] -job push(docker.io/timesu/busybox) = ERR (1) 

Please login prior to push:
Username: timesu
Password: 
Email: timesuss
EBU[0221] Calling POST /auth                           
INFO[0221] POST /v1.18/auth                             
INFO[0221] +job auth()                                  
INFO[0221] +job resolve_index(https://index.docker.io/v1/) 
INFO[0222] -job resolve_index(https://index.docker.io/v1/) = OK (0) 
DEBU[0222] pinging registry endpoint https://index.docker.io/v1/ 
DEBU[0222] attempting v1 ping for registry endpoint https://index.docker.io/v1/ 
DEBU[0222] attempting v1 login to registry endpoint https://index.docker.io/v1/ 
DEBU[0223] https://index.docker.io/v1/users/ -- HEADERS: map[User-Agent:[docker/1.6.2 go/go1.4.2 kernel/3.10.0-243.el7.x86_64 os/linux arch/amd64]] 


But once i pushed
# docker push time/busybox
DEBU[0425] pinging registry endpoint https://index.docker.io/v1/ 
DEBU[0425] attempting v1 ping for registry endpoint https://index.docker.io/v1/ 
Repository does not exist: docker.io/time/busybox
INFO[0425] -job push(time/busybox) = ERR (1)            
The push refers to a repository [docker.io/time/busybox] (len: 0)
FATA[0001] Repository does not exist: docker.io/time/busybox 

#docker tag time/busybox docker.io/time/busybox will workaround it, means 
#docker push time/busybox success after there is a docker.io/time/busybox
Comment 8 Luwen Su 2015-06-16 03:34:37 UTC 
In docker-1.6.2-14.el7.x86_64,
#docker pull busybox
#docker tag busybox timesu/busybox
#docker push timesu/busybox:latest# docker tag busybox:latest 
INFO[0033] POST /v1.18/images/timesu/busybox/push?force=1&tag=latest 
INFO[0033] +job push(timesu/busybox)                    
INFO[0033] +job resolve_repository(timesu/busybox)      
INFO[0033] -job resolve_repository(timesu/busybox) = OK (0) 

So move to verified
Comment 10 errata-xmlrpc 2015-06-23 09:29:30 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-1167.html
Note You need to log in before you can comment on or make changes to this bug.