Using the script at https://github.com/bkearney/soe-reference-architecture/blob/bk/container.sh I can not pull any of docker images from the satellite. Expected result: Be able to docker pull any of the items. Actual Result: 404 because they are protected.
Created redmine issue http://projects.theforeman.org/issues/10620 from this bug
Should be resolved when this gets merged https://github.com/Katello/katello/pull/5252/files
Moving to POST since upstream bug http://projects.theforeman.org/issues/10620 has been closed ------------- Partha Aji Applied in changeset commit:katello|70dda2a57fcf4f285b6952d073f93842331622ed.
commit b751e87d55be0ed16030fb00793b4ad699475495 Author: Partha Aji <paji> Date: Tue May 26 17:01:39 2015 -0400 Fixes #10620 - Repos no longer protected by default Repositories created via UI are not protected by default, however this is not the case for CLI. Repos created by the cli tend to have the protection on by default. This does not work well for docker, so trying to be consistent here. Also updated code to always set protected to false for docker type. This is because docker type does not have any protection at this time. more (cherry picked from commit 70dda2a57fcf4f285b6952d073f93842331622ed)
Verified on: S8C2 Steps to verify: 1) Ran the commands described on bug's description: hammer organization create --name "Container Org" hammer lifecycle-environment create --organization "Container Org" --name "DEV" --description "development" --prior "Library" hammer product create --name='containers' --organization="Container Org" hammer repository create --name='rhel' --organization="Container Org" --product='containers' --content-type='docker' --url='https://registry.access.redhat.com' --docker-upstream-name='rhel' --publish-via-http="true" hammer repository create --name='wordpress' --organization="Container Org" --product='containers' --content-type='docker' --url='https://registry.hub.docker.com' --docker-upstream-name='wordpress' --publish-via-http="true" hammer repository create --name='mysql' --organization="Container Org" --product='containers' --content-type='docker' --url='https://registry.hub.docker.com' --docker-upstream-name='mysql' --publish-via-http="true" hammer product synchronize --organization "Container Org" --name "containers" hammer content-view create --name "registry" --description "Sample Registry" --organization "Container Org" hammer content-view add-repository --organization "Container Org" --name "registry" --repository "rhel" --product "containers" hammer content-view add-repository --organization "Container Org" --name "registry" --repository "mysql" --product "containers" hammer content-view add-repository --organization "Container Org" --name "registry" --repository "wordpress" --product "containers" hammer content-view publish --organization "Container Org" --name "registry" 2) Searched for a repo id in order to pull images from and grabbed the published at info: hammer repository list --content-type docker --organization "Container Org" --content-view "registry" --lifecycle-environment "Library" hammer repository info --id 38 Published At: sat6server.com:5000/container_org-library-registry-containers-rhel 3) Installed the certificate RPM: [root@docker-host ~]# rpm -Uvh http://sat6server.com/pub/katello-ca-consumer-latest.noarch.rpm 4) Pulled the image: [root@docker-host ~]# docker pull sat6server.com:5000/container_org-library-registry-containers-rhel Trying to pull repository sat6server.com:5000/container_org-library-registry-containers-rhel ... 65de4a13fc7c: Download complete Status: Downloaded newer image for sat6server.com:5000/container_org-library-registry-containers-rhel:latest [root@docker-host ~]# docker images REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE sat6server.com:5000/container_org-library-registry-containers-rhel latest 65de4a13fc7c 5 weeks ago 154.9 MB
This bug is slated to be released with Satellite 6.1.
This bug was fixed in version 6.1.1 of Satellite which was released on 12 August, 2015.