# Private registry for system-docker

**URL:** <https://forums.suse.com/t/private-registry-for-system-docker/1658>\
**Category:** RancherOS\
**Created:** [February 7, 2016, 9:59pm UTC](https://forums.suse.com/t/private-registry-for-system-docker/1658 "2016-02-07T21:59:00Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![liyi](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/liyi/32/4609_2.png) [@liyi](https://forums.suse.com/u/liyi)\
**Post date:** [February 7, 2016, 9:59pm UTC](https://forums.suse.com/t/private-registry-for-system-docker/1658/1 "2016-02-07T21:59:00Z")

</div>

hi all  
do you know if it is possible to configure system-docker to access private registry? I want to have this because I would like to run a system service using a image from my private registry.  
Thanks a lot!

---

<div class="post-metadata">

**Author:** ![jwhitcraft](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/jwhitcraft/32/37_2.png) [@jwhitcraft](https://forums.suse.com/u/jwhitcraft)\
**Post date:** [February 8, 2016, 1:29pm UTC](https://forums.suse.com/t/private-registry-for-system-docker/1658/2 "2016-02-08T13:29:46Z")

</div>

I do this all the time, when i deploy my image, i just use an image name like this

> [registry.mycompany.net/awesomeimage:latest](http://registry.mycompany.net/awesomeimage:latest)

---

<div class="post-metadata">

**Author:** ![liyi](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/liyi/32/4609_2.png) [@liyi](https://forums.suse.com/u/liyi)\
**Post date:** [February 8, 2016, 2:13pm UTC](https://forums.suse.com/t/private-registry-for-system-docker/1658/3 "2016-02-08T14:13:46Z")

</div>

Maybe I was not clear enough. I mean a private registry with self-signed certificate or insecure mode. When I do so, it fails to pull down the image from my registry since it is not trustable.

---

<div class="post-metadata">

**Author:** ![bakchoy](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/bakchoy/32/915_2.png) [@bakchoy](https://forums.suse.com/u/bakchoy)\
**Post date:** [February 22, 2016, 2:48am UTC](https://forums.suse.com/t/private-registry-for-system-docker/1658/4 "2016-02-22T02:48:55Z")

</div>

I was searching how to do this as well (which is how I stumbled on this forum topic). I also found:

[https://github.com/rancher/os/issues/97](https://github.com/rancher/os/issues/97)

but that post is quite old (by Rancher OS standards at least) and it looks like the names of things have changed a bit. However, after reading it, I’m guessing that system-docker can be configured similarly to the user-docker.

So if I look at my “user” Docker config I see:  
[rancher@ranchy ~]$ sudo ros config get rancher.docker  
tls\_args:

- –tlsverify
- –tlscacert=/etc/docker/tls/ca.pem
- –tlscert=/etc/docker/tls/server-cert.pem
- –tlskey=/etc/docker/tls/server-key.pem
- -H=0.0.0.0:2376  
args:
- daemon
- –log-opt
- max-size=25m
- –log-opt
- max-file=2
- -s
- overlay
- -G
- docker
- -H
- unix:///var/run/docker.sock

And for my “system” Docker I see:  
[rancher@ranchy ~]$ sudo ros config get rancher.system\_docker  
args:

- daemon
- –log-opt
- max-size=25m
- –log-opt
- max-file=2
- -s
- overlay
- -b
- docker-sys
- –fixed-cidr
- 172.18.42.1/16
- –restart=false
- -g
- /var/lib/system-docker
- -G
- root
- -H
- unix:///var/run/system-docker.sock
- –userland-proxy=false

Although I haven’t tried it yet, I bet one could add the insecure flag to the rancher.system\_docker.args and then after restarting the system Docker should be able to access an insecure registry.