<p>I would check that all nodes are active and ready with command</p>

<pre><code>docker node ls
</code></pre>

<p>With </p>

<pre><code>docker swarm leave
</code></pre>

<p>and</p>

<pre><code>docker swarm join \
--token &lt;SWMTKN token&gt; \
&lt;manager private IP&gt;
</code></pre>

<p>you may rejoin malfunctioning node. </p>

CC BY-SA 3.0
2017-11-19T19:08:36.193Z
2017-11-19T19:08:36.193Z
mico
<p>For some unknown reason, the manager host which gets the command to launch a stack, tries to pile up all the containers on itself; other worker/manager hosts stay unemploed.</p>

<p>Unfortunately there are no log entries for that.</p>

<p>Has anybody observed this behaviour already with Docker CE as well?</p>

<docker><docker-swarm>
Strange orchestration behaviour of a Docker Swarm manager - pile of containers
Ta Mu
# Strange orchestration behaviour of a Docker Swarm manager - pile of containers

(Asked by: username_0 on 2017-11-09)

For some unknown reason, the manager host which gets the command to launch a stack, tries to pile up all the containers on itself; other worker/manager hosts stay unemploed.

Unfortunately there are no log entries for that.

Has anybody observed this behaviour already with Docker CE as well?

**Tags:** docker, docker-swarm


---

## 1 answers

### Answer by username_1 on 2017-11-19. Score: 1

I would check that all nodes are active and ready with command
docker node ls

With 
docker swarm leave

and
docker swarm join \
--token  \


you may rejoin malfunctioning node.


---

