Supported tags and respective Dockerfile links

• 2.7.0, 2.7, 2, latest (amd64/Dockerfile)
• 2.6.2, 2.6 (amd64/Dockerfile)
• 2.5.2, 2.5 (Dockerfile)

Quick reference

• Where to get help:
  the Docker Community Forums, the Docker Community Slack, or Stack Overflow

• Where to file issues:
  https://github.com/docker/distribution-library-image/issues

• Maintained by:
  Docker, Inc.

• Supported architectures: (more info)
  amd64, arm32v6, arm64v8

• Published image artifact details:
  repo-info repo's repos/registry/ directory (history)
  (image metadata, transfer size, etc)

• Image updates:
  official-images PRs with label library/registry
  official-images repo's library/registry file (history)

• Source of this description:
  docs repo's registry/ directory (history)

• Supported Docker versions:
  the latest release (down to 1.6 on a best-effort basis)

Docker Registry

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

Recommended Reading

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.

Support

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.

License

View license information for the software contained in this image.

As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).

Some additional license information which was able to be auto-detected might be found in the repo-info repository's registry/ directory.

As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.