Bridge network default behavior in Docker - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Default IP assignment in Docker bridge network

When you create a container attached to the default Docker bridge network, how is its IP address assigned?

A The container receives an IP address dynamically assigned from the bridge network's subnet by Docker's internal DHCP.

B The container receives a static IP address defined in the Dockerfile.

C The container shares the host machine's IP address directly without any separate IP.

D The container does not get any IP address unless manually configured.

💡 Hint

Think about how Docker manages networking for containers by default.

Docker's default bridge network uses an internal DHCP mechanism to assign IP addresses dynamically to containers from its subnet.

💻 Command Output

intermediate

Inspecting bridge network IP range

What is the output of the following command snippet that inspects the default bridge network's subnet?

docker network inspect bridge --format '{{range .IPAM.Config}}{{.Subnet}}{{end}}'

A 172.17.0.0/16

B 192.168.1.0/24

C 10.0.0.0/8

D No output, command fails

💡 Hint

The default Docker bridge network usually uses a private IP range starting with 172.

The default Docker bridge network typically uses the subnet 172.17.0.0/16 unless customized.

❓ Troubleshoot

advanced

Container cannot reach host on default bridge network

A container connected to the default bridge network cannot ping the host machine's IP address. What is the most likely reason?

A The container's IP address conflicts with the host's IP address.

B Docker disables inter-container communication by default on the bridge network.

C The host's firewall blocks traffic from the Docker bridge subnet.

D Containers on the default bridge network do not get DNS resolution.

💡 Hint

Consider network security settings on the host machine.

Host firewalls often block traffic from Docker bridge subnet IPs, preventing containers from reaching the host IP.

🔀 Workflow

advanced

Connecting two containers on default bridge network

You want two containers on the default bridge network to communicate by name. What must you do?

A Restart Docker daemon to enable container name resolution on the default bridge network.

B Manually edit /etc/hosts inside each container to add the other container's name and IP.

C Use the container's IP address directly because DNS is not supported on the default bridge network.

D Create a user-defined bridge network instead, which supports automatic DNS resolution by container name.

💡 Hint

Think about Docker's networking features for name resolution.

The default bridge network does not support automatic DNS resolution by container name. User-defined bridge networks do.

✅ Best Practice

expert

Securing default bridge network communication

What is the best practice to restrict container communication on the default Docker bridge network?

A Use Docker's --icc=false option to disable inter-container communication on the default bridge network.

B All of the above combined provide the best security.

C Configure iptables rules on the host to block unwanted container traffic on the default bridge network.

D Disable the default bridge network and create isolated user-defined bridge networks with specific rules.

💡 Hint

Consider multiple layers of network security controls.

Combining disabling inter-container communication, using isolated networks, and host firewall rules provides strong security.