How to get remote access to a private docker-registry

Question

I'm trying to setup a private docker registry using the image taken from:https://github.com/docker/docker-registry

I’m using the following command

docker run -p 5000:5000 registry

I can pull/push from/to this repository only from localhost, but if i try to access it from another machine (using a private address on the same LAN) it fails with an error message:

*2014/11/03 09:49:04 Error: Invalid registry endpoint https ://10.0.0.26:5000/v1/': Get https:// 10.0.0.26:5000/v1/_ping: Forbidden. If this private registry supports only HTTP or HTTPS with an unknown CA certificate, please add `--insecure-registry 10.0.0.26:5000` to the daemon's arguments. In the case of HTTPS, if you have access to the registry's CA certificate, no need for the flag; simply place the CA certificate at /etc/docker/certs.d/10.0.0.26:5000/ca.crt*

How do I fix this?

Answer 1

New client version refuses to work with a private registry without SSL.

The daemon on the client machine should be launched with the insecure flag

sudo service docker stop # to stop the service

and then

sudo docker -d --insecure-registry 10.0.0.26:5000

instead of 10.0.26:5000 use your own IP address.

Comments

Latest docker does not have the '-d' or '--insecure-registry' options.

Can you please update this blog based on latest docker version.

---

Hi@Anil,

you can use the below steps.

Edit your /lib/systemd/system/docker.service file and write down your registry IP address.

ExecStart=/usr/bin/dockerd -H fd:// –insecure-registry ip_address:5000