Skip to content
This repository has been archived by the owner on Sep 12, 2018. It is now read-only.

Docker private registry responsed with "Error response from daemon: Get https://xx:5000/v1/_ping: EOF" #1076

Open
soh0ro0t opened this issue Jun 2, 2016 · 3 comments

Comments

@soh0ro0t
Copy link

soh0ro0t commented Jun 2, 2016

  1. I build a private registry on a virtual machine, setup it with command below:
    docker run -d -p 5000:5000 --restart=always --name registry
    -v pwd/certs:/certs
    -e REGISTRY_HTTP_TLS_CERTIFICATE=/certs/domain.crt
    -e REGISTRY_HTTP_TLS_KEY=/certs/domain.key
    registry
  2. Then i run push/pull request to the registry on another virtual machine with command:
    docker pull xx:5000/debian

however, i got an err like this:
"Error response from daemon: Get https://xx:5000/v1/_ping: EOF", someone can help me?

@soh0ro0t
Copy link
Author

soh0ro0t commented Jun 2, 2016

in addtion, if i build private registry service on localhost, it is fine, no err occur.

@soh0ro0t
Copy link
Author

soh0ro0t commented Jun 2, 2016

in addtion, i found no docker messages on the host which run my private registry, seems it's nothing to do with the configuration but network between two virtual machine,.
i followed the instructions step by step:
https://github.com/docker/distribution/blob/master/docs/deploying.md#running-a-domain-registry

@koifans
Copy link

koifans commented Jul 31, 2018

I ran into the same situation. Any update for this issue? @thebeeman

[user0@vm ~]$ sudo docker login -u xx.com:5000
Password:
Error response from daemon: Get https://xx.com:5000/v1/users/: EOF

One thing I noticed is that I definitely run a v2 registry service but the error msg is still v1/user...

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants