Docker Registry Operations: Difference between revisions
Jump to navigation
Jump to search
| Line 23: | Line 23: | ||
docker run ... -v /mnt/registry:/var/lib/registry ... | docker run ... -v /mnt/registry:/var/lib/registry ... | ||
docker run -d -p 5000:5000 --restart=always -v /var/lib/registry:/var/lib/registry --name registry registry:2 | |||
Revision as of 23:25, 19 April 2018
External
- https://docs.docker.com/registry/
- https://docs.docker.com/registry/introduction/
- https://docs.docker.com/registry/deploying/
- https://docs.docker.com/registry/insecure/
Internal
Overview
"Docker Registry" in this context refers to the image published by Docker, which instantiates as a container that exposes the content of the local registry over TCP. Note that by default the Docker Registry container starts with HTTP support only, so all other Docker servers that use it must be configured to allow it as an "insecure registry", with --insecure-registry as described here.
Start
docker run -d -p 5000:5000 --restart=always --name registry registry:2
Customize Storage Location
docker run ... -v <native-host-path>:<container-mount-point> ...
docker run ... -v /mnt/registry:/var/lib/registry ...
docker run -d -p 5000:5000 --restart=always -v /var/lib/registry:/var/lib/registry --name registry registry:2