Bug 1389442
| Summary: | docker-1.12 can not pull image:tag from brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Johnny Liu <jialiu> |
| Component: | docker | Assignee: | Lokesh Mandvekar <lsm5> |
| Status: | CLOSED ERRATA | QA Contact: | atomic-bugs <atomic-bugs> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 7.3 | CC: | ajia, amurdaca, dwalsh, imcleod, lfriedma, lsm5, lsu, mitr |
| Target Milestone: | rc | Keywords: | Extras |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-01-17 20:43:44 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: | |||
|
Description
Johnny Liu
2016-10-27 15:14:34 UTC
I'm on it Fixed into this PR https://github.com/containers/image/pull/139 Waiting to merge that now, then rebuild for RHEL. (In reply to Antonio Murdaca from comment #3) > Fixed into this PR https://github.com/containers/image/pull/139 > Waiting to merge that now, then rebuild for RHEL. No rebuild for RHEL, first I need to re-vendor containers/image into our projectatomic/docker, then we'll rebuild for RHEL (Note that we can have a short-term fix, but this will completely prevent support for schema2 and manifest lists and the like. Both containers/image and docker seem to need need registries to report the correct MIME types.) (In reply to Miloslav Trmač from comment #5) > (Note that we can have a short-term fix, but this will completely prevent > support for schema2 and manifest lists and the like. Both containers/image > and docker seem to need need registries to report the correct MIME types.) Right, from now on, probably, those bugs need to target crane and pulp instead since we'll follow what docker does. docker branches fixed - assigning to Lokesh to rebuild in RHEL Fixed in docker-1.12.3 Re-test this bug with docker-1.12.3-1.el7.x86_64, still reproduce. # docker pull brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/openshift3/ose-pod:v3.4.0.16 Trying to pull repository brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/openshift3/ose-pod ... unsupported manifest media type application/x-troff-man docker-common-1.12.3-1.el7.x86_64 docker-1.12.3-1.el7.x86_64 docker-rhel-push-plugin-1.12.3-1.el7.x86_64 libselinux-2.5-6.el7.x86_64 libselinux-utils-2.5-6.el7.x86_64 libselinux-python-2.5-6.el7.x86_64 selinux-policy-targeted-3.13.1-102.el7.noarch container-selinux-1.12.3-1.el7.x86_64 selinux-policy-3.13.1-102.el7.noarch There must be an issue with packaging because I cannot reproduce building Docker from https://github.com/projectatomic/docker/commit/91ae1d15a5fee546a41c0442a4b33ad4f7a9fdf6 which is into docker-1.12.3 branch. dist git in RHEL for docker is wrong, this patch will likely fix this issue: diff --git a/docker.spec b/docker.spec index bd40f6d..18ed1bd 100644 --- a/docker.spec +++ b/docker.spec @@ -21,7 +21,7 @@ # docker %global git0 https://github.com/projectatomic/docker -%global commit0 5759a0805380f1067386e87b64f0e27ed818be27 +%global commit0 91ae1d15a5fee546a41c0442a4b33ad4f7a9fdf6 %global shortcommit0 %(c=%{commit0}; echo ${c:0:7}) # docker_branch used in %%check %global docker_branch docker-1.12.3 @@ -64,7 +64,7 @@ # docker-containerd %global git9 https://github.com/docker/containerd -%global commit9 0ac3cd1be170d180b2baed755e8f0da547ceb267 +%global commit9 b818e749726ba18e430bb825396c85408dfaf2a4 %global shortcommit9 %(c=%{commit9}; echo ${c:0:7}) # %%{name}-selinux stuff (prefix with ds_ for version/release etc.) This issue disappeared on docker-1.12.3-2.el7.x86_64. Confirmed, I hit it on docker-1.12.3-1.el7.x86_64 and problem is gone in 1:1.12.3-4.el7 Per comment#13 and #14 , move to verified 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/RHSA-2017-0116.html |