Lab
A Cloud Guru

Building a Private Docker Registry

Docker registries provide a powerful way to manage and distribute your Docker images. Docker offers a free registry at Docker Hub, but in many scenarios, you may want greater control of your images, not to mention that it is not free to have more than one private repository on Docker Hub. Fortunately, you can build and manage your own private registries, allowing you full control over where your images are housed and how they can be accessed. In this lab, you will have the opportunity to work with a private registry. You will build your own private registry, and you will have a chance to practice some advanced setup to ensure that your private registry is secure. After completing this lab, you will know how to set up a simple but secure private Docker registry.

Try for free Contact sales

Path Info

Level

Intermediate

Duration

1h 0m

Published

May 03, 2019

Challenge

Set up the private registry.
1. Create an htpasswd file containing the login credentials for the initial account.
2. Create a self-signed certificate for the registry. For the common name, enter the hostname of the registry server, which is ip-10-0-1-101.
3. Create a container to run the registry.
4. Once the registry starts up, verify that it is responsive. It's OK if this command returns nothing, just make sure it does not fail.
Challenge

Test the registry from the Docker workstation server.
Note: A private Docker registry is running on the Docker registry server using version 2.7 of the registry image.
1. Get the public hostname from the registry server. It should be ip-10-0-1-101.
2. Add the registry's public self-signed certificate to /etc/docker/certs.d. The scp command is copying the file from the registry server to the workstation. The password is the normal cloud_user password provided by the lab.
3. Log in to the private registry from the workstation. The credentials should be username docker and password d0ck3rrU73z.
4. Test the registry by pushing an image to it. You can pull any image from the Docker hub and tag it appropriately to push it to the registry as a test image.
5. Verify image pulling by deleting the image locally and re-pulling it from the private repository.

Author

A Cloud Guru

The Cloud Content team comprises subject matter experts hyper focused on services offered by the leading cloud vendors (AWS, GCP, and Azure), as well as cloud-related technologies such as Linux and DevOps. The team is thrilled to share their knowledge to help you build modern tech solutions from the ground up, secure and optimize your environments, and so much more!

What's a lab?

Hands-on Labs are real environments created by industry experts to help you learn. These environments help you gain knowledge and experience, practice without compromising your system, test without risk, destroy without fear, and let you learn from your mistakes. Hands-on Labs: practice your skills before delivering in the real world.