this change improves the instructions for swarm join-token and swarm init; - only print the join-token command for workers instead of for both managers and workers, to prevent users from copying the wrong command. An extra line is added to explain how to obtain the manager token. - print a message that a token was rotated sucesfully if '--rotate' is used. - add some extra white-space before / after the join commands, to make copy/pasting easier. this change also does some refactoring of join-token; - move flagname-constants together with other constants - use variables for selected role ("worker" / "manager") to prevent checking for them multiple times, and to keep the "worker" / "manager" sting centralized - add an extra blank line after "join-token" instructions this makes it easier to copy, and cleans up the code a tiny bit Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2.6 KiB
Add nodes to the swarm
Once you've created a swarm with a manager node, you're ready to add worker nodes.
-
Open a terminal and ssh into the machine where you want to run a worker node. This tutorial uses the name
worker1
. -
Run the command produced by the
docker swarm init
output from the Create a swarm tutorial step to create a worker node joined to the existing swarm:$ docker swarm join \ --token SWMTKN-1-49nj1cmql0jkz5s954yi3oex3nedyz0fb0xx14ie39trti4wxv-8vxv8rssmk743ojnwacrr2e7c \ 192.168.99.100:2377 This node joined a swarm as a worker.
If you don't have the command available, you can run the following command on a manager node to retrieve the join command for a worker:
$ docker swarm join-token worker To add a worker to this swarm, run the following command: docker swarm join \ --token SWMTKN-1-49nj1cmql0jkz5s954yi3oex3nedyz0fb0xx14ie39trti4wxv-8vxv8rssmk743ojnwacrr2e7c \ 192.168.99.100:2377
-
Open a terminal and ssh into the machine where you want to run a second worker node. This tutorial uses the name
worker2
. -
Run the command produced by the
docker swarm init
output from the Create a swarm tutorial step to create a second worker node joined to the existing swarm:$ docker swarm join \ --token SWMTKN-1-49nj1cmql0jkz5s954yi3oex3nedyz0fb0xx14ie39trti4wxv-8vxv8rssmk743ojnwacrr2e7c \ 192.168.99.100:2377 This node joined a swarm as a worker.
-
Open a terminal and ssh into the machine where the manager node runs and run the
docker node ls
command to see the worker nodes:ID HOSTNAME STATUS AVAILABILITY MANAGER STATUS 03g1y59jwfg7cf99w4lt0f662 worker2 Ready Active 9j68exjopxe7wfl6yuxml7a7j worker1 Ready Active dxn1zf6l61qsb1josjja83ngz * manager1 Ready Active Leader
The
MANAGER
column identifies the manager nodes in the swarm. The empty status in this column forworker1
andworker2
identifies them as worker nodes.Swarm management commands like
docker node ls
only work on manager nodes.
What's next?
Now your swarm consists of a manager and two worker nodes. In the next step of the tutorial, you deploy a service to the swarm.