Bug 1347805 - better error message when trying to pull from a integrate registry w/o being logged in.
Summary: better error message when trying to pull from a integrate registry w/o being ...
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: docker
Version: 7.4
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Antonio Murdaca
QA Contact: atomic-bugs@redhat.com
Depends On:
TreeView+ depends on / blocked
Reported: 2016-06-17 17:17 UTC by Peter Ruan
Modified: 2019-03-06 01:05 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2016-10-23 13:42:06 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Peter Ruan 2016-06-17 17:17:21 UTC
Description of problem:
  The error message when an unauthenticated user is trying to pull an image from an integrated registry is misleading.

Version-Release number of selected component (if applicable):
Docker version 1.10.3, build 02f13c2-unsupported

How reproducible:

Steps to Reproduce:
1. create and push an image an authenticated user
2. logout as the user
3. do docker pull <uploaded_image>

Actual results:
[root@host-8-172-77 ~]# docker images
REPOSITORY                                                                            TAG                 IMAGE ID            CREATED             SIZE                                            local               47bcc53f74dc        3 months ago        1.113 MB                                            local               47bcc53f74dc        3 months ago        1.113 MB                                            local               47bcc53f74dc        3 months ago        1.113 MB

[root@host-8-172-77 ~]# docker pull
Trying to pull repository ... 
Pulling repository
Error: image qp62u/tc487929-busybox not found

Expected results:
docker should give the error that the user is denied access because of authentication issue.

Additional info:

Comment 2 Daniel Walsh 2016-08-19 22:41:58 UTC
Shishir can I get an update on this?

Comment 3 Antonio Murdaca 2016-10-23 13:42:06 UTC
This is how docker/distribution and docker works as of today. You get a 404, thus an image not found, not because the image isn't there but because docker first attempts to pull from a V2 registry, it gets unauthorized, tries to contact a V1 registry, the V1 registry doesn't exists, it gets back a 404 which is then translated to an image not found. What you get at the end of this "probing" is just the last error in the chain (the image not found).
There are lengthy issues upstream about this (opened by me https://github.com/docker/docker/issues/21054, https://github.com/docker/docker/issues/19834), none of those are feasible because of how docker is designed today, and this design won't easily change in the near future (it could cost a huge compatibility issue).

I'm closing this as not a bug.

Comment 4 Daniel Walsh 2016-10-24 11:57:10 UTC
Is this worthy of a blog?  Just reference this bugzilla, talk about why this is and what it means.  Most of your content could be taken from the bugzilla.

Comment 5 Antonio Murdaca 2016-10-24 12:01:41 UTC
I've already written about this in this skopeo issue also https://github.com/projectatomic/skopeo/issues/235#issuecomment-254820427

I've added to my todo list to write a blog post about this (it'll be really short though)

Note You need to log in before you can comment on or make changes to this bug.