gotchadockerMinor

Strange orchestration behaviour of a Docker Swarm manager - pile of containers

Submitted by: @import:stackexchange-devops·Mar 10, 2026·

Viewed 0 times

swarmorchestrationdockerstrangebehaviourmanagercontainerspile

Problem

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?

Solution

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.

Code Snippets

docker node ls

docker swarm leave

docker swarm join \
--token <SWMTKN token> \
<manager private IP>

Context

StackExchange DevOps Q#2520, answer score: 1

Revisions (0)

No revisions yet.