title: do I need to manually tag "latest" when pushing to docker public repository?
body: <p>Suppose I have an image <code>me/mystuff:v0.0.1</code> </p>
  
  <p>I find if I push it to the repository:</p>
  
  <pre><code>docker push me/mystuff:v0.0.1 
  </code></pre>
  
  <p><code>latest</code> is not created, and on a pull from another machine it will complain, e.g. </p>
  
  <pre><code>ssh me@faraway
  (faraway)  $ docker run -it me/mystuff /bin/bash
  </code></pre>
  
  <p>will result in a not found error for <code>me/mystuff:latest</code>  </p>
  
  <p>I can add the latest tag and push explicitly to the public repository:</p>
  
  <pre><code>docker login me
  docker tag me/mystuff:v0.0.1 me/mystuff:latest
  docker push me/mystuff:latest
  </code></pre>
  
  <p>and then from another machine:</p>
  
  <pre><code>docker pull me/mystuff
  </code></pre>
  
  <p>will work because latest exists.</p>
  
  <p>I am also finding that once latest exists, it does not auto update when a new numbered version is pushed.</p>
  
  <p>Can I somehow eliminate this step of manually tagging latest and have latest automatically point to the latest numbered version?  </p>
  
  <p>Or is it there for a reason, like allowing the separation of development versions (tagged with a vN.N.N only) from the production version (tagged latest)?  </p>