{"action":"created","issue":{"url":"https://api.github.com/repos/docker/compose/issues/1175","labels_url":"https://api.github.com/repos/docker/compose/issues/1175/labels{/name}","comments_url":"https://api.github.com/repos/docker/compose/issues/1175/comments","events_url":"https://api.github.com/repos/docker/compose/issues/1175/events","html_url":"https://github.com/docker/compose/issues/1175","id":64276945,"number":1175,"title":"unable to pull from private registry","user":{"login":"natarajanv","id":11648755,"avatar_url":"https://avatars.githubusercontent.com/u/11648755?v=3","gravatar_id":"","url":"https://api.github.com/users/natarajanv","html_url":"https://github.com/natarajanv","followers_url":"https://api.github.com/users/natarajanv/followers","following_url":"https://api.github.com/users/natarajanv/following{/other_user}","gists_url":"https://api.github.com/users/natarajanv/gists{/gist_id}","starred_url":"https://api.github.com/users/natarajanv/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/natarajanv/subscriptions","organizations_url":"https://api.github.com/users/natarajanv/orgs","repos_url":"https://api.github.com/users/natarajanv/repos","events_url":"https://api.github.com/users/natarajanv/events{/privacy}","received_events_url":"https://api.github.com/users/natarajanv/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":16,"created_at":"2015-03-25T14:03:03Z","updated_at":"2015-06-10T18:40:43Z","closed_at":null,"body":"using compose version 1.2.0rc1, docker version 1.5.0\r\n\r\ngot this error when pulling image from private registry. The docker daemon is set with --insecure-regsitry=hostname:8443\r\n\r\nTraceback (most recent call last):\r\n  File \"<string>\", line 3, in <module>\r\n  File \"/code/build/docker-compose/out00-PYZ.pyz/compose.cli.main\", line 31, in main\r\n  File \"/code/build/docker-compose/out00-PYZ.pyz/compose.cli.docopt_command\", line 21, in sys_dispatch\r\n  File \"/code/build/docker-compose/out00-PYZ.pyz/compose.cli.command\", line 27, in dispatch\r\n  File \"/code/build/docker-compose/out00-PYZ.pyz/compose.cli.docopt_command\", line 24, in dispatch\r\n  File \"/code/build/docker-compose/out00-PYZ.pyz/compose.cli.command\", line 59, in perform_command\r\n  File \"/code/build/docker-compose/out00-PYZ.pyz/compose.cli.main\", line 464, in up\r\n  File \"/code/build/docker-compose/out00-PYZ.pyz/compose.project\", line 208, in up\r\n  File \"/code/build/docker-compose/out00-PYZ.pyz/compose.service\", line 214, in recreate_containers\r\n  File \"/code/build/docker-compose/out00-PYZ.pyz/compose.service\", line 197, in create_container\r\n  File \"/code/build/docker-compose/out00-PYZ.pyz/docker.client\", line 710, in pull\r\n  File \"/code/build/docker-compose/out00-PYZ.pyz/docker.auth.auth\", line 67, in resolve_repository_name\r\n  File \"/code/build/docker-compose/out00-PYZ.pyz/docker.auth.auth\", line 46, in expand_registry_url\r\ndocker.errors.DockerException: HTTPS endpoint unresponsive and insecure mode isn't enabled.\r\n\r\nWhen I add  --allow-insecure-ssl to the docker-compose, I get this error:\r\n\r\n  File \"/code/build/docker-compose/out00-PYZ.pyz/compose.service\", line 214, in recreate_containers\r\n  File \"/code/build/docker-compose/out00-PYZ.pyz/compose.service\", line 199, in create_container\r\n  File \"/code/build/docker-compose/out00-PYZ.pyz/compose.progress_stream\", line 37, in stream_output\r\n  File \"/code/build/docker-compose/out00-PYZ.pyz/compose.progress_stream\", line 50, in print_output_event\r\ncompose.progress_stream.StreamOutputError: Authentication is required.\r\n\r\nI confirmed that I am logged in by doing a docker pull from the private registry and it works fine.\r\n\r\nThanks for looking...\r\n\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/docker/compose/issues/comments/110872778","html_url":"https://github.com/docker/compose/issues/1175#issuecomment-110872778","issue_url":"https://api.github.com/repos/docker/compose/issues/1175","id":110872778,"user":{"login":"schmunk42","id":649031,"avatar_url":"https://avatars.githubusercontent.com/u/649031?v=3","gravatar_id":"","url":"https://api.github.com/users/schmunk42","html_url":"https://github.com/schmunk42","followers_url":"https://api.github.com/users/schmunk42/followers","following_url":"https://api.github.com/users/schmunk42/following{/other_user}","gists_url":"https://api.github.com/users/schmunk42/gists{/gist_id}","starred_url":"https://api.github.com/users/schmunk42/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/schmunk42/subscriptions","organizations_url":"https://api.github.com/users/schmunk42/orgs","repos_url":"https://api.github.com/users/schmunk42/repos","events_url":"https://api.github.com/users/schmunk42/events{/privacy}","received_events_url":"https://api.github.com/users/schmunk42/received_events","type":"User","site_admin":false},"created_at":"2015-06-10T18:40:43Z","updated_at":"2015-06-10T18:40:43Z","body":"> Does the image tag app_src:latest definitely exist locally when the service in question is started? If so, Compose should not attempt to pull it. Please open an issue if it does.\r\n\r\nIt does, but on `pull` and that should be kept as is I think, because `:latest` of an official repo could be updated. \r\n\r\nThe problem is, that we can not specify local images, because they can not be distinguished from official ones (besides the `_`, but just thinking loud here).\r\n\r\nI don't want't to build another image(-tag) from the same source, because it clutters my images list and costs some time also. Moreover, when working with single services, this could lead to different images.\r\n\r\nAs an addition to the above, `build` does work, but I am basically unable to use `docker-composer pull`, in a stack which contains local-only images, without throwing an error - and this would break our CI process."}}