title: when pushing docker image to private docker registry, having trouble marking it 'public' via my script (but can do via web ui)
body: <p>I am pushing a docker image to a private docker registry, and am having trouble marking it 'public' via 
  a script.</p>
  
  <p>For this discussion, I'm guessing the content of the Dockerfile doesn't matter... so lets assume I have the following in my 
  current working directory:</p>
  
  <p><em>Dockerfile</em></p>
  
  <pre><code>from ubuntu
  touch  /tmp/foo
  </code></pre>
  
  <p>I build like this:</p>
  
  <pre><code>docker build -t my.private.docker.registry.com/foo/jdk1.8.on.ubuntu14.04  . 
  </code></pre>
  
  <p>Then, I am doing my push like this:</p>
  
  <pre><code>docker push my.private.docker.registry.com/foo/jdk1.8.on.ubuntu14.04
  </code></pre>
  
  <p>Next, I navigate  to the web site that allows me to manage my private registry (@ the url <a href="http://my.private.docker.registry.com" rel="nofollow">http://my.private.docker.registry.com</a>)
  I look at my image, and I see it has a padlock icon next to it, indicating that it is private.  I can manually unlock from the 
  web UI, but I'd like to know if there are any options to docker's  'push command that will allow me to mark the image
  as 'public' without manual intervention.</p>
  
  <p>One thing I tried was setting global settings for my namespace such that all new repos would be readable/writable by all users.
  Specifically: I went into the Docker web ui for my private registry and for the namespace 'foo' I tried adding default permissions
  (for any newly created repos) such that all users will have 'write' access to any new repo pushed under the 'foo' namespace.</p>
  
  <p>However, even after doing the above, when I pushed a new image to my private registry under namespace foo, that image was still 
  marked with the pad-lock.  I looked up the command line options for 'docker push', and I did not see any option that looked like 
  it would affect the visibility of the image at the time of push.</p>
  
  <p>thanks in advance for your help !
   -chris</p>