Network drivers (bridge, host, overlay, none) in Docker - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Docker bridge network

Which statement best describes the Docker bridge network driver?

A It disables all networking for the container, isolating it completely.

B It connects containers directly to the host's network stack, sharing the host IP address.

C It creates a private internal network on the host where containers can communicate, isolated from the host network.

D It allows containers to communicate across multiple Docker hosts using an overlay network.

💡 Hint

Think about a private network inside the host for containers.

The bridge driver creates a private network internal to the host. Containers on this network can talk to each other but are isolated from the host network unless ports are published.

💻 Command Output

intermediate

Output of docker network inspect for host driver

What is the key difference in the output of docker network inspect host compared to a bridge network?

Docker

docker network inspect host

A The output shows an overlay network with multiple nodes connected.

B The output lists multiple IP addresses assigned to containers on a private subnet.

C The output indicates the network is disabled with no interfaces.

D The output shows containers share the host's network namespace with no IP address assigned to the network.

💡 Hint

Host network means no separate network namespace for containers.

The host network driver makes containers use the host's network stack directly, so no separate IP or subnet is assigned.

🔀 Workflow

advanced

Setting up multi-host communication with overlay network

Which sequence of commands correctly sets up an overlay network for containers across multiple Docker hosts?

A 3,1,2,4

B 1,2,3,4

C 2,1,3,4

D 1,3,2,4

💡 Hint

Initialize swarm before creating overlay network and joining nodes.

First, initialize swarm on manager (1), then create overlay network (2), join worker nodes (3), and finally deploy service on overlay (4).

❓ Troubleshoot

advanced

Diagnosing container network isolation with none driver

A container started with --network none cannot access the internet or other containers. What is the reason?

A The none driver disables all networking, so the container has no network interfaces.

B The container is connected to a private bridge network with no internet access.

C The container shares the host network but firewall blocks traffic.

D The overlay network is misconfigured causing isolation.

💡 Hint

None means no network at all.

The none network driver disables networking completely, so the container has no network interfaces and cannot communicate.

✅ Best Practice

expert

Choosing the right network driver for a secure web app

You want to deploy a web app container that must be isolated from other containers but accessible from the host on port 8080. Which network driver and configuration is best?

A Use bridge network and publish port 8080 to host, isolating containers but allowing host access.

B Use host network to share host IP and ports directly for best performance.

C Use none network and manually configure port forwarding on host.

D Use overlay network without publishing ports for container isolation.

💡 Hint

Isolate containers but allow host access on a port.

The bridge network isolates containers by default. Publishing port 8080 allows host access without exposing containers to each other.

Practice

1. Which Docker network driver allows containers on the same host to communicate using a private internal network?

easy

A. bridge

B. host

C. overlay

D. none

Solution

1. Step 1: Understand the purpose of the bridge driver

   The bridge driver creates a private network internal to the host, allowing containers to communicate securely on the same machine.

2. Step 2: Compare with other drivers

   The host driver uses the host's network directly, overlay connects containers across hosts, and none disables networking.

3. Final Answer:

   bridge -> Option A

4. Quick Check:

   Private internal network = bridge [OK]

Hint: Bridge = private network on one host [OK]

Common Mistakes:

• Confusing host with bridge driver
• Thinking overlay works on single host only
• Assuming none allows communication

2. Which command correctly creates a Docker container using the host network driver?

easy

A. docker run --network=bridge nginx

B. docker run --net=overlay nginx

C. docker run --network=host nginx

D. docker run --network=none nginx

Solution

1. Step 1: Identify the correct syntax for network option

   The correct flag is --network= followed by the driver name, e.g., host.

2. Step 2: Match the driver to the command

   docker run --network=host nginx uses --network=host which is the correct way to assign the host network driver.

3. Final Answer:

   docker run --network=host nginx -> Option C

4. Quick Check:

   Use --network=host for host driver [OK]

Hint: Use --network=host to assign host driver [OK]

Common Mistakes:

• Using --net=overlay instead of --network=overlay
• Confusing bridge and host flags
• Omitting the network flag

3. Given two Docker hosts connected with an overlay network named mynet, what will happen if you run docker network inspect mynet on one host?

medium

A. It shows no containers because overlay networks isolate containers

B. It shows only local bridge network details

C. It returns an error because overlay networks can't be inspected

D. It shows details of the overlay network including connected containers across hosts

Solution

1. Step 1: Understand overlay network scope

   Overlay networks span multiple Docker hosts, connecting containers across them.

2. Step 2: Inspect command behavior

   docker network inspect shows detailed info about the network, including containers connected on all hosts.

3. Final Answer:

   It shows details of the overlay network including connected containers across hosts -> Option D

4. Quick Check:

   Overlay network inspect shows multi-host details [OK]

Hint: Overlay networks span hosts; inspect shows all connected containers [OK]

Common Mistakes:

• Thinking overlay networks can't be inspected
• Assuming inspect shows only local containers
• Confusing overlay with none driver

4. You created a container with --network=none but it still can ping the host. What is the likely cause?

medium

A. The container has another network interface configured manually

B. The none driver allows all network traffic by default

C. Docker daemon is ignoring the network flag

D. The container is running in host network mode

Solution

1. Step 1: Understand the none network driver

   The none driver disables Docker-managed networking, so no automatic network interfaces are created.

2. Step 2: Analyze why container can ping host

   If the container can ping the host, it likely has a manually configured network interface inside the container.

3. Final Answer:

   The container has another network interface configured manually -> Option A

4. Quick Check:

   none disables Docker network; manual config allows connectivity [OK]

Hint: none disables Docker network; manual setup can override [OK]

Common Mistakes:

• Assuming none allows all traffic
• Thinking Docker ignores network flags
• Confusing none with host driver

5. You want to deploy a multi-host Docker Swarm service where containers communicate securely across hosts. Which network driver should you use and why?

hard

A. bridge, because it isolates containers on each host

B. overlay, because it connects containers across multiple hosts securely

C. host, because it uses the host network for better performance

D. none, because it disables networking for security

Solution

1. Step 1: Identify network needs for multi-host communication

   Containers on different hosts need a network driver that spans hosts and provides secure communication.

2. Step 2: Match drivers to requirements

   Bridge works only on one host, host shares host network (not multi-host), none disables networking, overlay connects containers across hosts securely.

3. Final Answer:

   overlay, because it connects containers across multiple hosts securely -> Option B

4. Quick Check:

   Multi-host secure communication = overlay [OK]

Hint: Overlay = multi-host secure network [OK]

Common Mistakes:

• Choosing bridge for multi-host
• Using host driver for container isolation
• Thinking none enables communication