title: Docker 1.6 and Registy 2.0
body: <p>Has anyone tried successfully the search command with Docker 1.6 and the new registry 2.0?</p>
  
  <p>I've set mine up behind Nginx with SSL, and so far it is working fine. I can <code>push</code> and <code>pull</code> images without problems. But when I try to <em>search</em> for them all the following command give a <code>404</code> response:</p>
  
  <pre><code>curl -k -s -X GET https://username:password@my-docker-registry.com/v1/search
  404 page not found
  
  curl -k -s -X GET https://username:password@my-docker-registry.com/v2/search
  404 page not found
  
  root@ip-10-232-0-191:~# docker search username:password@my-docker-registry.com/hello-world
  FATA[0000] Invalid repository name (admin:admin), only [a-z0-9-_.] are allowed
  
  root@ip-10-232-0-191:~# docker search my-docker-registry.com/hello-world
  FATA[0000] Error response from daemon: Unexpected status code 404
  </code></pre>
  
  <p>I wanted to ask if anyone has any ideas why and what is the correct way to use the Docker client to search the registry for images.</p>
  
  <p>Looking at the <a href="https://docs.docker.com/registry/spec/api/" rel="nofollow">API v2.0 documentation</a>, do they simply not support a <em>search</em> function? Seems a bit strange to omit such functionality.</p>
  
  <p>At least something works :)</p>
  
  <pre><code>root@ip-10-232-0-191:~# curl -k -s -X GET https://username:password@my-docker-registry.com/v2/hello-world/tags/list
  {"name":"hello-world","tags":["latest"]}
  </code></pre>