Swarm mode initialization in Docker - Mini Project: Build & Apply

Swarm Mode Initialization with Docker

📖 Scenario: You are setting up a Docker Swarm cluster to manage multiple Docker hosts as a single system. This helps in deploying and scaling containerized applications easily.

🎯 Goal: Learn how to initialize Docker Swarm mode on a manager node, configure the advertise address, and verify the swarm status.

📋 What You'll Learn

Initialize Docker Swarm mode on the local machine

Set the advertise address to 192.168.1.100

Verify the swarm status using Docker commands

💡 Why This Matters

🌍 Real World

Docker Swarm mode is used to manage multiple Docker hosts as a single cluster, making it easier to deploy, scale, and manage containerized applications in production.

💼 Career

Understanding swarm initialization is essential for DevOps roles that involve container orchestration and managing scalable application deployments.

1

Initialize Docker Swarm mode

Run the command docker swarm init with the option --advertise-addr 192.168.1.100 to initialize the swarm mode on your local machine.

Docker

# Run the docker swarm init command with the advertise address
# Your code here

Hint

Use docker swarm init --advertise-addr 192.168.1.100 exactly to start the swarm.

2

Check Swarm Node Status

Use the command docker node ls to list the nodes in the swarm and check the status of the current node.

Docker

docker swarm init --advertise-addr 192.168.1.100
# Run the command to list swarm nodes
# Your code here

Hint

Run docker node ls to see the swarm nodes and their status.

3

Verify Swarm Information

Run the command docker info and check that the output contains the line Swarm: active to confirm the swarm is active.

Docker

docker swarm init --advertise-addr 192.168.1.100
docker node ls
# Run the command to show detailed Docker info
# Your code here

Hint

Use docker info to see detailed Docker system information including swarm status.

4

Display Swarm Status Confirmation

Run docker info and print the output. The output should include the text Swarm: active confirming the swarm mode is enabled.

Docker

docker swarm init --advertise-addr 192.168.1.100
docker node ls
docker info
# Display the output of docker info to confirm swarm status
# Your code here

Hint

Look for Swarm: active in the output of docker info to confirm success.

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