docker swarm and private registry - docker

Question

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
or
curl 127.0.0.1:5000/v2/_catalog
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":[]}
Then on manager
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
I can see, that registry is running on worker2. So you can make pull/push/queries only on worker where image is running!?
My version of docker is:
Docker version 17.03.0-ce, build 60ccb22
What's am I doing wrong?

Answer 1

I'm answering to myself:
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.
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.