remote access to a private docker-registry -
i'm trying setup private docker registry using image taken from: https://github.com/docker/docker-registry
just running: docker run -p 5000:5000 registry
i can pull/push from/to repository localhost, if seek access machine (using private address on same lan) fails error message:
*2014/11/03 09:49:04 error: invalid registry endpoint https ://10.0.0.26:5000/v1/': https:// 10.0.0.26:5000/v1/_ping: forbidden. if private registry supports http or https unknown ca certificate, please add together `--insecure-registry 10.0.0.26:5000` daemon's arguments. in case of https, if have access registry's ca certificate, no need flag; place ca certificate @ /etc/docker/certs.d/10.0.0.26:5000/ca.crt*
what drives me crazy can access using: curl 10.0.0.26:5000
and/or curl 10.0.0.26:5000/v1/search
i don't understand , how should pass --insecure-registry
flag.
what missing here??? thanks!
ok - found solution - after day of digging. turns out new client version refuses work private registry without ssl.
to prepare - daemon on client machine should launched insecure flag:
just type:
sudo service docker stop # stop service
and
sudo docker -d --insecure-registry 10.0.0.26:5000
(replace 10.0.0.26
own ip address).
i expect docker guys add together alternative pull/push command line...
edit - altenantively - can add together flag docker_opts
env variable within /etc/default/docker... , sudo service docker restart
edit 1 time again - seems docker guys on - , prepare come soon: https://github.com/docker/docker/pull/8935
here's illustration of /etc/default/docker change:
docker_opts="$docker_opts --insecure-registry myregistry:5000"
docker remote-access docker-registry
No comments:
Post a Comment