{"action":"created","issue":{"url":"https://api.github.com/repos/openshift/origin/issues/9949","repository_url":"https://api.github.com/repos/openshift/origin","labels_url":"https://api.github.com/repos/openshift/origin/issues/9949/labels{/name}","comments_url":"https://api.github.com/repos/openshift/origin/issues/9949/comments","events_url":"https://api.github.com/repos/openshift/origin/issues/9949/events","html_url":"https://github.com/openshift/origin/issues/9949","id":166521060,"number":9949,"title":"Registry: Can not run registry on fresh new atomic host","user":{"login":"boskiv","id":1939783,"avatar_url":"https://avatars.githubusercontent.com/u/1939783?v=3","gravatar_id":"","url":"https://api.github.com/users/boskiv","html_url":"https://github.com/boskiv","followers_url":"https://api.github.com/users/boskiv/followers","following_url":"https://api.github.com/users/boskiv/following{/other_user}","gists_url":"https://api.github.com/users/boskiv/gists{/gist_id}","starred_url":"https://api.github.com/users/boskiv/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/boskiv/subscriptions","organizations_url":"https://api.github.com/users/boskiv/orgs","repos_url":"https://api.github.com/users/boskiv/repos","events_url":"https://api.github.com/users/boskiv/events{/privacy}","received_events_url":"https://api.github.com/users/boskiv/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/openshift/origin/labels/component/imageregistry","name":"component/imageregistry","color":"0052cc"},{"url":"https://api.github.com/repos/openshift/origin/labels/kind/question","name":"kind/question","color":"cc317c"},{"url":"https://api.github.com/repos/openshift/origin/labels/priority/P2","name":"priority/P2","color":"fbca04"}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2016-07-20T08:03:44Z","updated_at":"2016-07-20T13:35:15Z","closed_at":null,"body":"I have tried to run registry on Centos 7.2 host with atomic util installed. \r\nBut it does not run\r\nAfter it I have install fresh new atomic centos host and run commands from Quick start documentation\r\n```\r\nsudo atomic install projectatomic/atomic-registry-quickstart\r\nsudo atomic run projectatomic/atomic-registry-quickstart\r\n```\r\nBut registry can not start. (the same issue)\r\n\r\nPlease help me to find reason.\r\n\r\nI have only one network interface with static ip adress.\r\n\r\n\r\n```\r\n[deploy@registry ~]$ sudo atomic install projectatomic/atomic-registry-quickstart\r\nUsing default tag: latest\r\nTrying to pull repository docker.io/projectatomic/atomic-registry-quickstart ... \r\nlatest: Pulling from docker.io/projectatomic/atomic-registry-quickstart\r\na3ed95caeb02: Pull complete \r\n5989106db7fb: Pull complete \r\n52b97052a83a: Pull complete \r\n9ee8a6cc8ad7: Pull complete \r\n940329aac7dd: Pull complete \r\na5a5d20cbf6c: Pull complete \r\nDigest: sha256:9501aa14f623553fbb63907d35cfc47b483c13de02da79e5ea1c2b04ed81f21b\r\nStatus: Downloaded newer image for docker.io/projectatomic/atomic-registry-quickstart:latest\r\ndocker run -i --rm --privileged --net=host -v /var/run:/var/run:rw -v /sys:/sys -v /etc/localtime:/etc/localtime:ro -v /var/lib/docker:/var/lib/docker:rw -v /var/lib/origin/:/var/lib/origin/ -v /etc/origin/:/etc/origin/ -v /:/host -e KUBECONFIG=/etc/origin/master/admin.kubeconfig --entrypoint /container/bin/install.sh projectatomic/atomic-registry-quickstart\r\nUsing default tag: latest\r\nTrying to pull repository docker.io/openshift/origin ... \r\nlatest: Pulling from docker.io/openshift/origin\r\na3ed95caeb02: Already exists\r\nda71393503ec: Pulling fs layer\r\na3ed95caeb02: Pulling fs layer\r\n05f9edd312a3: Pulling fs layer\r\na86b97e1f9bb: Pulling fs layer\r\na86b97e1f9bb: Waiting\r\na3ed95caeb02: Verifying Checksum\r\na3ed95caeb02: Download complete\r\n05f9edd312a3: Verifying Checksum\r\n05f9edd312a3: Download complete\r\na86b97e1f9bb: Verifying Checksum\r\na86b97e1f9bb: Download complete\r\nda71393503ec: Verifying Checksum\r\nda71393503ec: Download complete\r\nda71393503ec: Pull complete\r\nda71393503ec: Pull complete\r\na3ed95caeb02: Pull complete\r\na3ed95caeb02: Pull complete\r\n05f9edd312a3: Pull complete\r\n05f9edd312a3: Pull complete\r\na86b97e1f9bb: Pull complete\r\na86b97e1f9bb: Pull complete\r\nDigest: sha256:35c5ef338cd75eb14b3793304eba2cc3892cbccd9e0bb302736fd4c7ad466a5a\r\nStatus: Downloaded newer image for docker.io/openshift/origin:latest\r\nUsing default tag: latest\r\nTrying to pull repository docker.io/openshift/origin-docker-registry ... \r\nGet https://registry-1.docker.io/v2/openshift/origin-docker-registry/manifests/latest: Get https://auth.docker.io/token?scope=repository%!A(MISSING)openshift%!F(MISSING)origin-docker-registry%!A(MISSING)pull&service=registry.docker.io: net/http: request canceled while waiting for connection\r\nGet https://registry-1.docker.io/v2/openshift/origin-docker-registry/manifests/latest: Get https://auth.docker.io/token?scope=repository%3Aopenshift%2Forigin-docker-registry%3Apull&service=registry.docker.io: net/http: request canceled while waiting for connection\r\nUsing default tag: latest\r\nTrying to pull repository docker.io/cockpit/kubernetes ... \r\nlatest: Pulling from docker.io/cockpit/kubernetes\r\n14707640923f: Pulling fs layer\r\n017afeaf9d5d: Pulling fs layer\r\na7a4f7287840: Pulling fs layer\r\n017afeaf9d5d: Verifying Checksum\r\n017afeaf9d5d: Download complete\r\na7a4f7287840: Verifying Checksum\r\na7a4f7287840: Download complete\r\n14707640923f: Verifying Checksum\r\n14707640923f: Download complete\r\n14707640923f: Pull complete\r\n14707640923f: Pull complete\r\n017afeaf9d5d: Pull complete\r\n017afeaf9d5d: Pull complete\r\na7a4f7287840: Pull complete\r\na7a4f7287840: Pull complete\r\nDigest: sha256:d7a4b8c3ed2cc7f796d6a6a75c849ca6ca0ad947ee4e7fd18e8d5a7a3579e702\r\nStatus: Downloaded newer image for docker.io/cockpit/kubernetes:latest\r\nInstalling using hostname registry.dev.nl.exness.local\r\nWrote master config to: /etc/origin/master/master-config.yaml\r\n+ mv /host/etc/origin/node-registry.dev.nl.exness.local /host/etc/origin/node\r\nCopy files to host\r\n+ mkdir -p /host/etc/origin/registry/bin\r\n+ mkdir -p /host/etc/origin/master/site\r\n+ cp /container/bin/install.sh /container/bin/run.sh /container/bin/uninstall.sh /host/etc/origin/registry/bin/.\r\n+ cp /container/etc/origin/registry-console-template.yaml /host/etc/origin/registry/.\r\n+ cp /container/etc/origin/registry-newproject-template-shared.json /host/etc/origin/registry/.\r\n+ cp /container/etc/origin/registry-newproject-template-unshared.json /host/etc/origin/registry/.\r\n+ cp /container/etc/origin/registry-login-template.html /host/etc/origin/master/site/.\r\n+ cat /etc/origin/master/master.server.crt /etc/origin/master/master.server.key\r\nUpdating servicesNodePortRange to 80-32767...\r\n+ set +x\r\nUpdating login template\r\nOptionally edit configuration file /etc/origin/master/master-config.yaml,\r\nadd certificates to /etc/origin/master,\r\nthen run 'atomic run projectatomic/atomic-registry-quickstart'\r\n[deploy@registry ~]$ sudo atomic run projectatomic/atomic-registry-quickstart\r\ndocker run -i --rm --privileged --net=host -v /:/host -v /var/lib/docker:/var/lib/docker:rw -v /etc/origin:/etc/origin -v /var/lib/registry:/var/lib/registry -e KUBECONFIG=/etc/origin/master/admin.kubeconfig --entrypoint /container/bin/run.sh projectatomic/atomic-registry-quickstart\r\n\r\nThis container uses privileged security switches:\r\n\r\nINFO: --net=host \r\n      Processes in this container can listen to ports (and possibly rawip traffic) on the host's network.\r\n\r\nINFO: --privileged \r\n      This container runs without separation and should be considered the same as root on your system.\r\n\r\nFor more information on these switches and their security implications, consult the manpage for 'docker run'.\r\n\r\nRunning using hostname registry.dev.nl.exness.local\r\n427426c3b35c597eb57246b30c3eb87522d6317ad11a5c030ea213a10063c963\r\nWaiting for services to come up...\r\n{\r\n  \"kind\": \"APIVersions\",\r\n  \"versions\": [\r\n    \"v1\"\r\n  ],\r\n  \"serverAddressByClientCIDRs\": [\r\n    {\r\n      \"clientCIDR\": \"0.0.0.0/0\",\r\n      \"serverAddress\": \"10.129.4.6:443\"\r\n    }\r\n  ]\r\n}\r\nStarting registry services...\r\n+ chroot /host docker exec -i origin oadm registry --latest-images=true\r\n--> Creating registry registry ...\r\n    serviceaccount \"registry\" created\r\n    clusterrolebinding \"registry-registry-role\" created\r\n    deploymentconfig \"docker-registry\" created\r\n    service \"docker-registry\" created\r\n--> Success\r\n+ chroot /host docker exec -i origin oc patch service docker-registry -p '{ \"spec\": { \"type\": \"NodePort\", \"selector\": {\"docker-registry\": \"default\"}, \"ports\": [ {\"nodePort\": 5000, \"port\": 5000, \"targetPort\": 5000}] }}'\r\n\"docker-registry\" patched\r\n+ set +x\r\n+ chroot /host docker exec -i origin oc create -f /etc/origin/registry/registry-console-template.yaml\r\nStarting web UI service...\r\ntemplate \"registry-console-template\" created\r\n+ chroot /host docker exec -i origin oc new-app --template registry-console-template -p OPENSHIFT_OAUTH_PROVIDER_URL=https://registry.dev.nl.exness.local:8443,COCKPIT_KUBE_URL=https://registry.dev.nl.exness.local,REGISTRY_HOST=registry.dev.nl.exness.local:5000\r\n--> Deploying template registry-console-template for \"registry-console-template\"\r\n     With parameters:\r\n      OPENSHIFT_OAUTH_PROVIDER_URL=https://registry.dev.nl.exness.local:8443\r\n      COCKPIT_KUBE_URL=https://registry.dev.nl.exness.local\r\n      COCKPIT_KUBE_INSECURE=\r\n      OPENSHIFT_OAUTH_CLIENT_SECRET=usered6UOXlEuMcCweQHwjIr8wsRiStLyDWoqRwklrxnVmBDlEdiP0x0btWrYOLrGSbI # generated\r\n      OPENSHIFT_OAUTH_CLIENT_ID=cockpit-oauth-client\r\n      KUBERNETES_INSECURE=\r\n      KUBERNETES_CA_DATA=\r\n      REGISTRY_HOST=registry.dev.nl.exness.local:5000\r\n--> Creating resources ...\r\n    deploymentconfig \"registry-console\" created\r\n    service \"registry-console\" created\r\n    imagestream \"registry-console\" created\r\n    oauthclient \"cockpit-oauth-client\" created\r\n--> Success\r\n    Run 'oc status' to view your app.\r\n+ chroot /host docker exec -i origin oc patch service registry-console -p '{ \"spec\": { \"type\": \"NodePort\", \"selector\": {\"name\": \"registry-console\"}, \"ports\": [ {\"name\": \"https\", \"nodePort\": 443, \"port\": 9000, \"targetPort\": 9090}, {\"name\": \"http\", \"nodePort\": 80, \"port\": 9000, \"targetPort\": 9090} ] }}'\r\n\"registry-console\" patched\r\nUpdating default project configuration\r\n+ set +x\r\n+ chroot /host docker exec -i origin oc create -f /etc/origin/registry/registry-newproject-template-shared.json\r\ntemplate \"registry-newproject-template-shared\" created\r\n+ chroot /host docker exec -i origin oc create -f /etc/origin/registry/registry-newproject-template-unshared.json\r\ntemplate \"registry-newproject-template-unshared\" created\r\n+ sed -i 's/  projectRequestTemplate:.*$/  projectRequestTemplate: \"default\\/registry-newproject-template-shared\"/' /etc/origin/master/master-config.yaml\r\nRestarting API server\r\n+ set +x\r\n+ chroot /host docker restart origin\r\norigin\r\n+ set +x\r\nWeb UI hosted at https://registry.dev.nl.exness.local\r\nError deleting container: Error response from daemon: Unable to remove filesystem for c8bc4fd70c572e450be93c81ab52ab6c6485d9a61263b06deb0649c0dd69996d: remove /var/lib/docker/containers/c8bc4fd70c572e450be93c81ab52ab6c6485d9a61263b06deb0649c0dd69996d/shm: device or resource busy\r\n```"},"comment":{"url":"https://api.github.com/repos/openshift/origin/issues/comments/233950463","html_url":"https://github.com/openshift/origin/issues/9949#issuecomment-233950463","issue_url":"https://api.github.com/repos/openshift/origin/issues/9949","id":233950463,"user":{"login":"aweiteka","id":1764461,"avatar_url":"https://avatars.githubusercontent.com/u/1764461?v=3","gravatar_id":"","url":"https://api.github.com/users/aweiteka","html_url":"https://github.com/aweiteka","followers_url":"https://api.github.com/users/aweiteka/followers","following_url":"https://api.github.com/users/aweiteka/following{/other_user}","gists_url":"https://api.github.com/users/aweiteka/gists{/gist_id}","starred_url":"https://api.github.com/users/aweiteka/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/aweiteka/subscriptions","organizations_url":"https://api.github.com/users/aweiteka/orgs","repos_url":"https://api.github.com/users/aweiteka/repos","events_url":"https://api.github.com/users/aweiteka/events{/privacy}","received_events_url":"https://api.github.com/users/aweiteka/received_events","type":"User","site_admin":false},"created_at":"2016-07-20T13:35:15Z","updated_at":"2016-07-20T13:35:15Z","body":"@boskiv I'm in the process of recommending a different installation approach. While I try to reproduce this issue would you be willing to try it out?\r\n\r\nFirst, uninstall the current, failed installation\r\n```\r\nsudo atomic uninstall projectatomic/atomic-registry-quickstart\r\n```\r\nThen follow this procedure: https://hub.docker.com/r/projectatomic/atomic-registry-install/ (Source[1])\r\nCorresponding documentation will land in http://docs.projectatomic.io/registry/ pending this PR under review: https://github.com/openshift/openshift-docs/pull/2471\r\n\r\n[1] https://github.com/openshift/origin/tree/master/examples/atomic-registry/systemd"}}
{"actor":{"display_login":"aweiteka"}}