Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1418939

Summary: docker pull with private registry (Artifactory) fails to request bearer token
Product: Red Hat Enterprise Linux 7 Reporter: Antonio Murdaca <amurdaca>
Component: dockerAssignee: Daniel Walsh <dwalsh>
Status: CLOSED ERRATA QA Contact: atomic-bugs <atomic-bugs>
Severity: high Docs Contact:
Priority: unspecified    
Version: 7.3CC: adimania, admiller, amurdaca, dwalsh, extras-qa, ichavero, james.hogarth, jcajka, jchaloup, lsm5, lsu, marianne, mark, mattias.hofvander, miminar, nalin, obockows, riek, sara.c, vbatts
Target Milestone: rcKeywords: Extras
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Pulling images from additional registries like Artifactory was not requesting authorization properly. We have fixed this issue in this release.
Story Points: ---
Clone Of: 1413987 Environment:
Last Closed: 2017-05-26 14:32:50 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1413987    
Bug Blocks:    

Comment 1 Antonio Murdaca 2017-02-03 08:39:16 UTC
Fixed in docker-1.12.6

Comment 3 James Hogarth 2017-02-27 15:49:59 UTC
Any timeline on when this might be built and pushed to the extras channel?

We have a preference for artifactory and this is a blocker for some of our usage.

Comment 4 Daniel Walsh 2017-02-27 16:56:57 UTC
This should be in our next release, which is supposed to be released shortly.

Fixed in docker-1.12.6-11.el7

Comment 8 Luwen Su 2017-05-16 08:22:18 UTC
I'm not sure if this is enough for verifying, if anything is wrong, please correct me.

Per https://bugzilla.redhat.com/show_bug.cgi?id=1403908 comment#3
and https://github.com/containers/image/pull/191/files

Just make sure the pull from individual repository is worked fine. 

docker-1.12.6-26.git62520c0.el7.x86_64

# docker pull docker.io/timesu/test-push1
Using default tag: latest
Trying to pull repository docker.io/timesu/test-push1 ... 
latest: Pulling from docker.io/timesu/test-push1
Digest: sha256:501b4aeda663174f1b6243c5acec2fa403884dba9ae4bff99a3f3e9190582503

Comment 10 errata-xmlrpc 2017-05-26 14:32:50 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://access.redhat.com/errata/RHBA-2017:1325