Private registry

Learn to run your own private registry.

A private registry

To run your own registry, the official registry:2 image is enough. Images are tagged with the registry address at the start of the name and pushed:

docker run -d --name registry -p 5000:5000 -v registry-veri:/var/lib/registry registry:2
docker tag api:1.0 localhost:5000/api:1.0
docker push localhost:5000/api:1.0
curl http://localhost:5000/v2/_catalog
# {"repositories":["api"]}

TLS and managed registries

Docker talks to registries other than localhost only over HTTPS. In production a registry is protected with a TLS certificate and authentication; or a managed service is used: GitHub (ghcr.io), GitLab, AWS ECR, Google Artifact Registry, Azure ACR. They all use the same login/tag/push flow.

docker tag api:1.0 registry.sirket.com/ekip/api:1.0
docker login registry.sirket.com
docker push registry.sirket.com/ekip/api:1.0

Exercise A local registry

Write three commands: start a container named registry from registry:2 in the background publishing port 5000 with the same number; tag api:1.0 as localhost:5000/api:1.0; push it.

Show example solution

docker run -d --name registry -p 5000:5000 registry:2
docker tag api:1.0 localhost:5000/api:1.0
docker push localhost:5000/api:1.0

Test yourself

What must the image name be to push it to the registry at localhost:5000?
- localhost:5000/api:1.0
- api:1.0@localhost
- 5000/api:1.0
- api:localhost:5000
Show answer

localhost:5000/api:1.0 — If the first part of the name contains a dot or colon, it counts as a registry address.

List the repositories in the registry.

curl http://localhost:5000/v2/____

Show answer

curl http://localhost:5000/v2/_catalog

Match.

registry:2

Your own registry
localhost:5000/

Target registry prefix
/v2/_catalog

Repository list
ECR, ACR

Managed registry

Next lesson: Summary - Registry

We Are Enhancing Your Experience

Cookie Preferences

Strictly Necessary Cookies

Analytical Cookies