Description of problem: Tagged pull from a private registry returns 404 Not found. docker pull -a from same registry pulls the image including the tagged one. Version-Release number of selected component (if applicable): docker-1.8.2-7.el7.x86_64 How reproducible: Always Steps to Reproduce: 1. setup private registry 2. pull tagged image ~~~ [root@docker ~]# docker pull satellite:5000/red_hat-engineering-ccv-rhel7-docker_image1-rhel:7.1-9 Trying to pull repository satellite:5000/red_hat-engineering-ccv-rhel7-docker_image1-rhel ... not found Tag 7.1-9 not found in repository satellite:5000/red_hat-engineering-ccv-rhel7-docker_image1-rhel ~~~ 3. downgrade docker and pull ~~~ root@docker ~]# yum downgrade docker <snip> Removed: docker.x86_64 0:1.8.2-7.el7 <snip> Installed: docker.x86_64 0:1.7.1-115.el7 [root@docker ~]# docker pull satellite:5000/red_hat-engineering-ccv-rhel7-docker_image1-rhel:7.1-9 Trying to pull repository satellite:5000/red_hat-engineering-ccv-rhel7-docker_image1-rhel ... e3c92c6cff35: Download complete Status: Downloaded newer image for satellite:5000/red_hat-engineering-ccv-rhel7-docker_image1-rhel:7.1-9 ~~ Actual results: Tagged pull returns 404 not found. Expected results: Success full tagged pull as with docker-1.7.1-115. Additional info:
Michal any ideas?
Seems to come from pulp-crane plugin. Issue seems to be solved after applying https://github.com/pulp/crane/commit/d4ef8967901651680e0febd3ff54333c86fafed0 [root@docker ~]# rpm -qa | grep docker docker-selinux-1.8.2-7.el7.x86_64 docker-1.8.2-7.el7.x86_64 docker-registry-0.9.1-7.el7.x86_64 [root@docker ~]# docker pull satellite:5000/red_hat-engineering-ccv-rhel7-docker_image1-rhel:7.1-9 Trying to pull repository satellite:5000/red_hat-engineering-ccv-rhel7-docker_ie3c92c6cff35: Pulling image (7.1-9) from satellite:5000/red_hat-engineering-ccve3c92c6cff35: Pulling image (7.1-9) from satellite:5000/red_hat-engineering-ccve3c92c6cff35: Download complete Status: Downloaded newer image for satellite:5000/red_hat-engineering-ccv-rhel7-docker_image1-rhel:7.1-9
*** This bug has been marked as a duplicate of bug 1282431 ***