Swarm mode initialization in Docker - Commands & Configuration

Introduction

When you want to run multiple Docker containers across several machines as one group, you use Swarm mode. Initializing Swarm mode sets up your machine as the manager that controls this group.

When you want to manage a cluster of Docker hosts as a single system.

When you need to deploy services that can scale across multiple servers.

When you want automatic load balancing between containers running on different machines.

When you want to easily add or remove machines from your container cluster.

When you want to ensure high availability by having multiple managers in your cluster.

Commands

This command starts Swarm mode on your current machine and makes it the manager. The --advertise-addr flag tells other machines how to reach this manager.

Terminal

docker swarm init --advertise-addr 192.168.1.100

Expected Output

Swarm initialized: current node (abcdef123456) is now a manager.



To add a worker to this swarm, run the following command:

    docker swarm join --token SWMTKN-1-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 192.168.1.100:2377



To add a manager to this swarm, run 'docker swarm join-token manager' and follow the instructions.

→

--advertise-addr - Specifies the IP address or interface that other nodes use to connect to this manager.

This command lists all nodes in the Swarm cluster to verify the manager is active and see any joined nodes.

Terminal

docker node ls

Expected Output

ID                            HOSTNAME            STATUS              AVAILABILITY        MANAGER STATUS      ENGINE VERSION

abcdef123456                  my-manager          Ready               Active              Leader              20.10.12

Key Concept

If you remember nothing else from this pattern, remember: initializing Swarm mode turns your machine into the manager that controls your container cluster.

Common Mistakes

Not specifying the correct IP address with --advertise-addr.

Other machines cannot connect to the manager if the advertised address is wrong or unreachable.

Use the machine's real network IP address reachable by other nodes in the cluster.

Trying to initialize Swarm mode on a machine that is already part of another Swarm.

The command will fail because a node cannot be manager of two different Swarms at once.

Leave the existing Swarm first using 'docker swarm leave --force' before initializing a new one.

Summary

Run 'docker swarm init --advertise-addr <IP>' to start Swarm mode and make your machine the manager.

Use 'docker node ls' to check the status of nodes in your Swarm cluster.

The manager controls the cluster and other machines join it using the join token.

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