Creating a private Docker registry

All Yours

The End Is Nigh

As you have seen, the process of setting up a private registry is quite simple, even if it is a little fiddly in parts. The ability to set up a registry with a large number of usernames means that removing access is easy on an individual basis. The registry container's logs show which IP addresses are connecting and the images those IP addresses are pulling from and pushing to your registry. Because you are using certificates, you can be certain of encrypted connections to the registry to prevent interception of your valuable images.

To go one step further, some online suggestions are about load balancing container image registries for a "productionized" approach. Additionally, you can tweak the storage driver being used and change some of the file path settings to better point at large storage devices, if required. Armed with the basics in this article, you should be well placed to try more advanced settings with relative ease.


  1. Install Docker Engine on Ubuntu:

The Author

Chris Binnie's latest book, Linux Server Security: Hack and Defend, shows how hackers launch sophisticated attacks to compromise servers, steal data, and crack complex passwords, so you can learn how to defend against such attacks. In the book, he also shows you how to make your servers invisible, perform penetration testing, and mitigate unwelcome attacks. You can find out more about DevOps, DevSecOps, Containers, and Linux security on his website:

Buy this article as PDF

Express-Checkout as PDF
Price $2.95
(incl. VAT)

Buy ADMIN Magazine

Get it on Google Play

US / Canada

Get it on Google Play

UK / Australia

Related content

comments powered by Disqus
Subscribe to our ADMIN Newsletters
Subscribe to our Linux Newsletters
Find Linux and Open Source Jobs

Support Our Work

ADMIN content is made possible with support from readers like you. Please consider contributing when you've found an article to be beneficial.

Learn More”>


		<div class=