{"action":"closed","issue":{"url":"https://api.github.com/repos/docker/distribution/issues/958","labels_url":"https://api.github.com/repos/docker/distribution/issues/958/labels{/name}","comments_url":"https://api.github.com/repos/docker/distribution/issues/958/comments","events_url":"https://api.github.com/repos/docker/distribution/issues/958/events","html_url":"https://github.com/docker/distribution/issues/958","id":105193382,"number":958,"title":"Issue running docker registry on coreos","user":{"login":"madhurranjan","id":596447,"avatar_url":"https://avatars.githubusercontent.com/u/596447?v=3","gravatar_id":"","url":"https://api.github.com/users/madhurranjan","html_url":"https://github.com/madhurranjan","followers_url":"https://api.github.com/users/madhurranjan/followers","following_url":"https://api.github.com/users/madhurranjan/following{/other_user}","gists_url":"https://api.github.com/users/madhurranjan/gists{/gist_id}","starred_url":"https://api.github.com/users/madhurranjan/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/madhurranjan/subscriptions","organizations_url":"https://api.github.com/users/madhurranjan/orgs","repos_url":"https://api.github.com/users/madhurranjan/repos","events_url":"https://api.github.com/users/madhurranjan/events{/privacy}","received_events_url":"https://api.github.com/users/madhurranjan/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/docker/distribution/labels/question","name":"question","color":"cc317c"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-09-07T10:43:53Z","updated_at":"2015-09-08T19:46:00Z","closed_at":"2015-09-08T19:46:00Z","body":"Hi,\r\nBelow is the docker version I'm running:\r\n$ docker --version\r\nDocker version 1.6.2, build 7c8fca2-dirty\r\n\r\nThe only time I'm able to get docker registry(registry:2) to run is when I run the following command:\r\ndocker run -d -p 80:5000 --restart=always --name registry \\\r\n  -v `pwd`/certs:/certs \\\r\n  -e REGISTRY_HTTP_TLS_CERTIFICATE=/certs/domain.crt \\\r\n  -e REGISTRY_HTTP_TLS_KEY=/certs/domain.key \r\n\r\nWhen I try running it with a 'config.yaml' for the exact same options, it doesn't work. \r\n\r\n```\r\n$ cat config.yaml\r\nversion: 0.1\r\nstorage:\r\n  filesystem:\r\n    rootdirectory: /var/lib/registry\r\nlog:\r\n  level: debug\r\nhttp:\r\n  addr: 0.0.0.0:80\r\n  tls:\r\n    certificate: /certs/domain.crt\r\n    key: /certs/domain.key\r\n  debug:\r\n    addr: localhost:5001\r\n```\r\n\r\nI use the following command to start it:\r\n\r\n```\r\n$ docker run -d -p 80:5000 --restart=always --name registry -v `pwd`/config.yml:/etc/docker/registry/config.yml -v `pwd`/certs:/certs registry:2\r\n```\r\n\r\nWhen I try to push an image, I see \r\n Error response from daemon: v1 ping attempt failed with error: Get https://< >:80/v1/_ping: tls: oversized record received with length 20527. If this private registry supports only HTTP or HTTPS with an unknown CA certificate, please add `--insecure-registry <>:80` to the daemon's arguments. \r\n\r\n$docker logs registry \r\ntime=\"2015-09-07T10:40:22.574469683Z\" level=debug msg=\"filesystem.List(\\\"/\\\")\" instance.id=75ce54a3-909e-4fbc-ae2c-a2f68209de26 trace.duration=74.425µs trace.file=\"/go/src/github.com/docker/distribution/registry/storage/driver/base/base.go\" trace.func=\"github.com/docker/distribution/registry/storage/driver/base.(*Base).List\" trace.id=00860c8e-fb4a-4ead-95fc-4c697c1860bf trace.line=123 version=v2.1.1 \r\n\r\nI have the right ssl certificates in place so not sure why its not working. Eventual goal is to get it working with S3 but even that is not working , when I provide values via command line ( REGISTRY_STORAGE_S3_REGION, REGISTRY_STORAGE_S3_BUCKET and REGISTRY_STORAGE_S3_ROOTDIRECTORY) or when I provide S3 values in the yaml. \r\n\r\nCan someone help me out here please?"}}