Swarm mode initialization in Docker - Step-by-Step Execution

Process Flow - Swarm mode initialization

Run 'docker swarm init'

↓

Docker checks current node state

↓

Not in swarm

↓

Initialize swarm

↓

Create manager node

↓

Generate join tokens

↓

Swarm mode active

This flow shows how running 'docker swarm init' checks the node state, initializes the swarm if not already in one, creates a manager node, generates join tokens, and activates swarm mode.

Execution Sample

Docker

docker swarm init
# Initializes the current node as a swarm manager

This command starts swarm mode on the current Docker node, making it a manager.

Process Table

Step	Action	Evaluation	Result
1	Run 'docker swarm init'	Check if node is already in swarm	Node not in swarm, proceed
2	Initialize swarm	Create swarm cluster and manager node	Swarm initialized, node is manager
3	Generate join tokens	Create tokens for worker and manager nodes	Tokens generated and stored
4	Output join command	Display command to add other nodes	Join command shown to user
5	Swarm mode active	Node state updated	Node is now in swarm mode as manager

💡 Swarm mode initialized successfully; node is now a manager in the swarm cluster

Status Tracker

Variable	Start	After Step 2	After Step 5
Node State	Not in swarm	Swarm initialized, manager node	Swarm mode active, manager node
Join Tokens	None	Generated	Available for other nodes

Key Moments - 2 Insights

Why does 'docker swarm init' fail if the node is already part of a swarm?

Because the command checks the node state first (see execution_table step 1). If the node is already in a swarm, it will not re-initialize and returns an error or info message.

What are join tokens and why are they important?

Join tokens are secret strings generated during initialization (step 3) that allow other nodes to securely join the swarm as workers or managers.

Visual Quiz - 3 Questions

Look at the execution table, what is the node state immediately after step 2?

A Node is not in swarm

B Swarm initialized, node is manager

C Join tokens generated

D Swarm mode active

💡 Hint

Check the 'Result' column for step 2 in the execution_table

At which step are join tokens created?

A Step 1

B Step 2

C Step 3

D Step 4

💡 Hint

Look at the 'Action' and 'Result' columns in the execution_table for token generation

If the node was already part of a swarm, what would happen when running 'docker swarm init'?

A Command returns error or info, no changes made

B Swarm re-initializes and overwrites existing cluster

C Join tokens are regenerated

D Node leaves swarm and rejoins

💡 Hint

Refer to the decision point in concept_flow and step 1 in execution_table

Concept Snapshot

docker swarm init
- Initializes current node as swarm manager
- Checks if node is already in swarm
- Creates swarm cluster and manager node
- Generates join tokens for other nodes
- Activates swarm mode on this node

Full Transcript

When you run 'docker swarm init', Docker first checks if the current node is already part of a swarm. If it is not, Docker creates a new swarm cluster and makes this node the manager. It then generates join tokens that other nodes can use to join the swarm as workers or managers. Finally, the node state updates to indicate it is now in swarm mode as a manager. If the node is already in a swarm, the command will not re-initialize and will return an error or information message. This process ensures secure and proper setup of swarm mode on your Docker node.

Practice

1. What is the main purpose of running docker swarm init?

easy

A. To add a new worker node to an existing swarm

B. To create a new Docker swarm cluster and make the current node a manager

C. To remove a node from a swarm

D. To update Docker to the latest version

Solution

1. Step 1: Understand the command purpose

   docker swarm init is used to start a new swarm cluster and make the current node the manager.

2. Step 2: Differentiate from other swarm commands

   Adding nodes uses docker swarm join, not init. Removing nodes or updating Docker are unrelated.

3. Final Answer:

   To create a new Docker swarm cluster and make the current node a manager -> Option B

4. Quick Check:

   Swarm init = create manager node [OK]

Hint: Init creates manager; join adds workers [OK]

Common Mistakes:

• Confusing init with join command
• Thinking init updates Docker
• Assuming init removes nodes

2. Which of the following is the correct syntax to initialize a swarm with a specific advertise address?

easy

A. docker swarm create --advertise 192.168.1.10

B. docker swarm start --advertise-addr 192.168.1.10

C. docker swarm init --advertise-addr 192.168.1.10

D. docker swarm init -a 192.168.1.10

Solution

1. Step 1: Recall correct command syntax

   The correct command to initialize swarm with advertise address is docker swarm init --advertise-addr <IP>.

2. Step 2: Identify incorrect options

   docker swarm start and docker swarm create are invalid commands. The short flag -a is not recognized for advertise address.

3. Final Answer:

   docker swarm init --advertise-addr 192.168.1.10 -> Option C

4. Quick Check:

   Use --advertise-addr with init [OK]

Hint: Use full flag --advertise-addr with init [OK]

Common Mistakes:

• Using 'start' or 'create' instead of 'init'
• Using short flag '-a' which is invalid
• Omitting --advertise-addr flag

3. What will be the output of the command docker swarm init --advertise-addr 10.0.0.5 if the node is already part of a swarm?

medium

A. Error: This node is already part of a swarm

B. Swarm initialized successfully with advertise address 10.0.0.5

C. Warning: Advertise address ignored, node already in swarm

D. Swarm initialized but advertise address not set

Solution

1. Step 1: Understand swarm init behavior on existing swarm node

   If a node is already in a swarm, running docker swarm init again causes an error because it cannot reinitialize.

2. Step 2: Check output messages

   The command will output an error message indicating the node is already part of a swarm, not success or warning.

3. Final Answer:

   Error: This node is already part of a swarm -> Option A

4. Quick Check:

   Init on existing swarm node = error [OK]

Hint: Init fails if node already in swarm [OK]

Common Mistakes:

• Assuming init overwrites existing swarm
• Expecting a warning instead of error
• Thinking advertise address is ignored silently

4. You ran docker swarm init --advertise-addr 192.168.0.100 but other nodes cannot join the swarm. What is the most likely problem?

medium

A. The join token expired immediately after init

B. You forgot to run docker swarm join on the manager node

C. Swarm mode is not supported on this Docker version

D. The advertise address is set to an IP not reachable by other nodes

Solution

1. Step 1: Analyze advertise address role

   The advertise address tells other nodes where to connect. If it is set to an IP unreachable by others, they cannot join.

2. Step 2: Evaluate other options

   Join tokens are used on worker nodes, not manager. Swarm mode is supported in modern Docker versions. Join tokens do not expire immediately.

3. Final Answer:

   The advertise address is set to an IP not reachable by other nodes -> Option D

4. Quick Check:

   Advertise address must be reachable [OK]

Hint: Check advertise IP reachability for joining nodes [OK]

Common Mistakes:

• Trying to join on manager node
• Assuming join tokens expire instantly
• Ignoring network connectivity issues

5. You want to initialize a swarm on a node with multiple network interfaces. Which command ensures other nodes connect via the interface with IP 172.16.5.10?

hard

A. docker swarm init --advertise-addr 172.16.5.10

B. docker swarm init --listen-addr 172.16.5.10

C. docker swarm init --advertise-addr eth1

D. docker swarm init --interface 172.16.5.10

Solution

1. Step 1: Identify correct flag for advertise address

   The --advertise-addr flag sets the IP address other nodes use to connect to the manager.

2. Step 2: Eliminate incorrect options

   --listen-addr sets the address the manager listens on internally, not what others connect to. Using interface name or unknown flags is invalid.

3. Final Answer:

   docker swarm init --advertise-addr 172.16.5.10 -> Option A

4. Quick Check:

   Use --advertise-addr with IP for multi-interface nodes [OK]

Hint: Use IP with --advertise-addr, not interface name [OK]

Common Mistakes:

• Using --listen-addr instead of --advertise-addr
• Passing interface name instead of IP
• Using unsupported flags like --interface