library/registryMaintained by:
the Docker Community
Where to get help:
CNCF community slack, or Stack Overflow
Dockerfile linksWhere to file issues:
https://github.com/distribution/distribution-library-image/issues
Supported architectures: (more info)
amd64, arm32v6, arm32v7, arm64v8, ppc64le, riscv64, s390x
Published image artifact details:
repo-info repo’s repos/registry/ directory (history)
(image metadata, transfer size, etc)
Image updates:
official-images repo’s library/registry label
official-images repo’s library/registry file (history)
Source of this description:
docs repo’s registry/ directory (history)
This image contains an implementation of the OCI Distribution spec. See github.com/opencontainers/distribution-spec for more details about what it is. You can find the full source code in github.com/distribution/distribution.
$ 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 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.
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.