私人码头注册和高可用性 [英] Private docker registry and high availability

问题描述

我们正在一台托管我们所有图像的服务器上运行私有注册表。
如果服务器崩溃，我们基本上会松动我们所有的图像。我们想找到一种方法来实现我们的图像的高可用性。
我看到一个简单的解决方案是每个服务器都有一个注册表实例。
负载平衡器会将流量重定向（循环）到可用的注册表实例。注册表实例将共享相同的网络数据驱动器（NFS）以存储图像。

We are currently running a private registry on one server hosting all our images on it. If the server crash, we basically loose all our images. We would like to find a way to enable high availability on our images. An easy solution I see would be to have a registry instance per server. A load balancer would redirect(Round robin) the traffic to ones of the registry instances available. Registry instances would share the same network data drive(NFS) to store the images.

您是否看到此解决方案有任何问题？
ie：如果用户在实例上推送映像，另一个按另一个（负载均衡器轮询决定），它会在NFS上创建任何锁定文件吗？

Do you see any problems with this solution ? i.e: If a user push an image on an instance, and another push on another ( Load balancer round robin decision), would it create any lock files on the NFS ?

感谢您的反馈

推荐答案

有一些有关Docker注册表网站上的信息。简而言之，它似乎旨在支持多个注册管理机构与同一个数据存储交谈，因此您不应该看到任何问题。

There is some information on this on the docker-registry website. In short, it seems designed to support multiple registries talking to the same data-store so you shouldn't see any problems.

如果可靠性是一个真正的问题，查看其中一个商业产品可能是明智的，例如企业中心或 CoreOS Enterprise Registry 。 （虽然这些似乎强调安全和访问控制而不是HA）。

If reliability is a real issue for you, it might be wise to look at one of the commercial offerings e.g. enterprise Hub or the CoreOS Enterprise Registry. (Although these seem to stress security and access controls rather than HA).

这篇关于私人码头注册和高可用性的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！