Jul 18

Synchronize Docker Images between Private Docker Registry Instances

Posted: under Cloud, container.
Tags: , , , , July 18th, 2016

From the Devops prospective, it seems managing Docker images in a production environment is much harder than doing so in a development environment. In a production system, you need a reliable, secure and efficient way to manage images. The open source enterprise class Private Docker Registry Harbor is the tool I like most.

In Harbor, you can set privilege of a user to access a docker repository. As an administrator of a production system, I don’t want anyone to have the privilege to push an image to the registry which distributes images to production machines. Harbor helps secure the production environment.

My favorite feature of Harbor is the ability to replicate images between registry instances.  There is more than one registry server in our environment, the images on these registry servers must be in sync to deliver the same images. Harbor automatically synchronizes images between registry instances, which save a lot of effort in maintaining the same images on different registry. Harbor can even retry when it encounters error during replication. Without Harbor, one probably needs to write quite a few scripts to synchronize images between instances. For any ops manager, this is almost a must-have function.

Harbor comes with a friendly GUI, it is very simple to use. I highly recommend Harbor for managing an organization’s private docker images. Here is its github URL: https://github.com/vmware/harbor

 

Comments (0)