-
Notifications
You must be signed in to change notification settings - Fork 1.1k
swarm cluster provisioned with docker-machine does not seem to distribute workloads #428
Comments
@ehazlett can you take a look |
Seems to be azure specific, the crate team were successful on gce |
Cc @jeffmendoza |
Caveat. I haven't looked at this yet. However,
|
@nmackenzie |
How long did it block for? It's quite possible it's blocking pulling the image. When you create a container on a Swarm, it pulls the image for that container but doesn't report back pulling status with progress bars like usual – it just hangs. See #349 for a potential fix for this. |
I tested this again, with a cluster provisioned with machine 0.2, and it works.
|
Maybe I'm getting the doc wrong.
I provision a 3 machine cluster according to docker-machine documentation.
If I try to do
it blocks
Talking to the docker daemon on master directly works.
But then I get no benefit from swarm, a second invocation, instead of scheduling on another node, barfs on port conflict.
swarm-master runs 2 containers: swarm-agent on port 2376 and swarm manage on port 3376.
I understand I should be talking to swarm manage.
The logs are not very helpful:
Are secure swarm clusters based on docker-machine deployment something that is not yet fully implemented?
Or is there something missing in the docs?
Or do I miss something in my config?
The text was updated successfully, but these errors were encountered: