title: Pushing files into private registry in Docker
body: <p>I have setup the private registry using <code>docker run -t -i -p 5000:5000 registry</code> and it is accessible from <strong>192.168.59.103:5000</strong> (I am using <strong>boot2docker</strong>). Now I have already pulled an image <strong>tutum/tomcat</strong> and when I try to push the image (<code>docker push 192.168.59.103:5000/tomcat</code>) into the registry after tagging it as <strong>192.168.59.103:5000/tomcat</strong> I face the following error as shown below --</p>
  
  <pre><code>FATA[0004] Error: v1 ping attempt failed with error: Get https://192.168.59.103:5000/v1/_ping: EOF. If this private regi
  stry supports only HTTP or HTTPS with an unknown CA certificate, please add `--insecure-registry 192.168.59.103: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/192.168.59.103:5000/ca.crt
  </code></pre>
  
  <p><strong>FROM OTHER POSTS --</strong></p>
  
  <p>I have read some some posts about this where they state that adding <strong>DOCKER_OPTS</strong> would solve the issue and that it should be added into <strong>/etc/default/docker</strong> but In my system <strong>/etc/default</strong> doesn't contain a <strong>docker</strong> folder as shown from the command <code>sudo ls /etc/default/</code> which provides the result as a sungle folder <strong>aufs</strong>.</p>
  
  <p>Another post states that this can be thrawted by simply placing the certificate att <strong>/etc/docker/certs.d/192.168.59.103:5000/ca.crt</strong> but I am <strong>not able to move into the docker directory even when I use sudo</strong> as seen below -- for <code>cd /etc/docker</code></p>
  
  <p><code>-sh: cd: can't cd to /etc/docker</code></p>
  
  <p>I have repeated the same process using the registry ip as 0.0.0.0:5000 inside docker (with the assumption the that <code>$boot2docker ip</code> should be used in the hosts machine and not within docker) -- But that still didn't fix the issue that I am facing.</p>
  
  <p>Please do help me out to sort out this problem. I have added the system specification below --</p>
  
  <p>System Specification:</p>
  
  <pre><code>Microsoft Windows 7 via. boot2docker (CLI version 1.5)
  Client version: 1.5.0
  Client API version: 1.17
  Go version (client): go1.4.1
  Git commit (client): a8a31ef
  OS/Arch (client): linux/amd64
  Server version: 1.5.0
  Server API version: 1.17
  Go version (server): go1.4.1
  Git commit (server): a8a31ef
  </code></pre>