Swarm mode initialization in Docker - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Swarm Initialization Output

What is the typical output when you run docker swarm init successfully on a new Docker host?

Docker

docker swarm init

A

Swarm initialized: current node (id) is now a manager.
To add a worker to this swarm, run the following command:
docker swarm join --token <worker_token> <manager_ip>:2377

B Error response from daemon: This node is already part of a swarm.

C

Usage: docker swarm init [OPTIONS]
Try 'docker swarm init --help' for more information.

D Swarm join token is invalid. Please check the token and try again.

💡 Hint

Think about what message confirms the node became a manager and gives instructions for adding workers.

When you run 'docker swarm init' on a fresh Docker host, it initializes the swarm and makes the node a manager. The output confirms this and provides the command to add worker nodes.

🧠 Conceptual

intermediate

Swarm Mode Initialization Requirements

Which of the following is a required condition before running docker swarm init on a host?

A The host must already be part of another swarm.

B The Docker CLI must be installed but the daemon can be stopped.

C The Docker daemon must be running and the host must have a unique hostname.

D The host must have at least 4 CPUs and 16GB RAM.

💡 Hint

Consider what is essential for Docker to manage containers and identify the node uniquely.

To initialize a swarm, the Docker daemon must be running to manage containers, and the host needs a unique hostname to identify it in the swarm.

❓ Troubleshoot

advanced

Swarm Init Failure Due to Network Conflict

You run docker swarm init but get the error: Error starting daemon: Error initializing network controller: Error creating default "bridge" network: network with name bridge already exists. What is the most likely cause?

A A Docker network named 'bridge' already exists, causing a conflict during swarm initialization.

B The Docker daemon is not running, so the network cannot be created.

C The host firewall is blocking port 2377 required for swarm communication.

D The Docker CLI version is outdated and incompatible with swarm mode.

💡 Hint

Think about what the error message says about the 'bridge' network.

The error indicates a network named 'bridge' already exists, which conflicts with swarm's attempt to create its default network. Removing or renaming the existing network resolves this.

🔀 Workflow

advanced

Steps to Add a Worker Node to a Swarm

After initializing a swarm on the manager node, what is the correct sequence of commands to add a new worker node to the swarm?

A 1,2,3,4

B 3,1,2,4

C 1,3,2,4

D 1,2,4

💡 Hint

Remember that worker nodes do not run 'docker swarm init'.

The correct workflow is to get the join command from the manager, run it on the worker node, then verify on the manager. Worker nodes do not initialize swarm themselves.

✅ Best Practice

expert

Best Practice for Swarm Manager Node Initialization

Which practice is recommended when initializing a Docker Swarm manager node to ensure high availability and security?

A Initialize the swarm without specifying an advertise address to let Docker choose automatically.

B Initialize the swarm with the <code>--autolock</code> flag to encrypt swarm keys and require a unlock key on restart.

C Use the <code>docker swarm init --force-new-cluster</code> option on the first manager node.

D Disable TLS encryption to improve swarm communication speed.

💡 Hint

Think about how to protect swarm secrets and manager keys.

Using the --autolock flag encrypts swarm keys at rest, requiring a key to unlock the swarm after manager restart, improving security and availability.

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