Supported tags and respective
For more information about this image and its history, please see the relevant manifest file (
library/registry). This image is updated via pull requests to the
docker-library/official-images GitHub repo.
For detailed information about the virtual/transfer sizes and individual layers of each of the above supported tags, please see the
repos/registry/tag-details.md file in the
docker-library/repo-info GitHub repo.
This image contains an implementation of the Docker Registry HTTP API V2 for use with Docker 1.6+. See github.com/docker/distribution for more details about what it is.
Run a local registry: Quick Version
$ docker run -d -p 5000:5000 --restart always --name registry registry:2
Now, use it from within Docker:
$ docker pull ubuntu $ docker tag ubuntu localhost:5000/ubuntu $ docker push localhost:5000/ubuntu
The documentation over at docs.docker.com is a good place to learn more about what the registry is, how it works, and how to use it.
Specifically, the section regarding deployment has pointers for more complex use cases than simply running a registry on localhost.
If you are interested in commercial support, the Docker Trusted Registry provides an image registry, LDAP/Active Directory integration, security certificates, and more in a solution that includes commercial support.
Supported Docker versions
This image is officially supported on Docker version 1.13.0.
Support for older versions (down to 1.6) is provided on a best-effort basis.
Please see the Docker installation documentation for details on how to upgrade your Docker daemon.
If you have any problems with or questions about this image, please contact us through a GitHub issue. If the issue is related to a CVE, please check for a
cve-tracker issue on the
official-images repository first.
You can also reach many of the official image maintainers via the
#docker-library IRC channel on Freenode.
You are invited to contribute new features, fixes, or updates, large or small; we are always thrilled to receive pull requests, and do our best to process them as fast as we can.
Before you start to code, we recommend discussing your plans through a GitHub issue, especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give you feedback on your design, and help you find out if someone else is working on the same thing.
Documentation for this image is stored in the
registry/ directory of the
docker-library/docs GitHub repo. Be sure to familiarize yourself with the repository's
README.md file before attempting a pull request.
where is the docker-registry v1 0.9.1 image?
and how can i get that?
While pushing to the new registry From v1 to v2, i got the below error message /var/lib/docker/devicemapper/mnt/e0d1095bc883a580d60a2a29542536b3870742ea7295451504a5e159cac0c588/rootfs/.wh..wh.plnk/588.249615: no such file or directory.
Kindly help me to proceed further ..
docker run -d --net=host --restart=always --name registry \
-e "REGISTRY_AUTH=htpasswd" \
-e "REGISTRY_AUTH_HTPASSWD_REALM=Registry Realm" \
-e REGISTRY_HTTP_TLS_CERTIFICATE=/certs/domain.crt \
-e REGISTRY_HTTP_TLS_KEY=/certs/domain.key \
i run this cmd ,and docker logs registry
panic: unable to configure authorization (htpasswd): "path" must be set for htpasswd access controller
goroutine 1 [running]:
please update the docs! version 2.5.0 writes it's data to /var/lib/registry and NOT to /tmp/registry-dev
don't forget to specify the version your want, such as docker mention here : https://docs.docker.com/registry/deploying/
such as an exemple : docker run -d -p 5000:5000 --restart=always --name registry registry:2
how to set a username and password
docker pull latest registry, bash into container, found a bunch of py code, cool?
s3 storage drive doesn't support region 'ap-northeast-2'.
Please fix this.
I'm also interested in a registry image, that is not run as root. What is the reason to run the registry as root?