码头群和私人登记 [英] docker swarm and private registry

问题描述

我尝试测试docker群组和私人注册表作为服务，而不使用TLS：1个经理和2个工作人员。经理：

I try to test docker swarm and private registry as a service without TLS: 1 manager and 2 worker. On manager:

docker service create --name registry --publish 5000:5000 registry:2

当试图检查经理时，使用

When trying to check on manager, with

curl localhost:5000/v2/_catalog

或

curl 127.0.0.1:5000/v2/_catalog

卷曲只是等待（至少一个小时）。在工作1上相同但是对于工作人员2工程确定！

curl just wait for ever (at least an hour). Same on worker1. but on worker 2 works ok!

 curl 127.0.0.1:5000/v2/_catalog
{"repositories":[]}

然后在经理

docker service ps registry
ID            NAME        IMAGE       NODE                DESIRED STATE  CURRENT STATE         ERROR  PORTS
p6ngzdemfolu  registry.1  registry:2  worker2  Running        Running 14 hours ago

我可以看到，该注册表在worker2上运行。因此，您只能在运行图像的工作人员进行拉/推/查询！？

I can see, that registry is running on worker2. So you can make pull/push/queries only on worker where image is running!?

我的版本是：
Docker版本17.03.0-ce ，建立60ccb22

My version of docker is: Docker version 17.03.0-ce, build 60ccb22

我做错了什么？

推荐答案

我回答自己：

我把经理转移到了google，并在scenegroup上添加了一个worker。工人之间有所有需要的港口打开。所以我的组合是GCE上的经理+工作人员，AWS上的工作人员和SCENE上的工作人员。

I moved manager to google and add one more worker on scenegroup. between workers there is all needed ports open. So my combination is manager+worker on GCE, worker on AWS and worker on SCENE.

当AWS工作人员流失时，所有似乎都可以正常工作。如果AWS工作人员处于活动状态，则群发问题。我自己的决定是，google和亚马逊。

All seems to work ok, when AWS worker is drained. If AWS worker active, there is problems with swarm. My own decision is, that there is something between google & amazon.

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