Why container networking matters in Docker - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why do containers need networking?

Which of the following best explains why container networking is important?

A Containers use networking only to access the host's file system.

B Containers use networking only to download images from Docker Hub.

C Networking is not needed because containers run isolated and never interact.

D Containers need networking to communicate with each other and external systems.

💡 Hint

Think about how multiple containers work together in an application.

Containers often run parts of an application that must talk to each other or to outside services. Networking allows this communication.

💻 Command Output

intermediate

Inspecting Docker container network settings

What is the output of the following command if a container named webapp is running and connected to the default bridge network?

Docker

docker inspect -f '{{json .NetworkSettings.Networks }}' webapp

A {"bridge":{"IPAMConfig":null,"Links":null,"Aliases":null,"NetworkID":"abc123","EndpointID":"def456","Gateway":"172.17.0.1","IPAddress":"172.17.0.2","IPPrefixLen":16,"IPv6Gateway":"","GlobalIPv6Address":"","GlobalIPv6PrefixLen":0,"MacAddress":"02:42:ac:11:00:02","DriverOpts":null}}

B Error: No such container: webapp

C {}

D {"host":{}}

💡 Hint

The default Docker network is called bridge and containers get an IP in the 172.17.0.0/16 range.

The command shows the network details of the container. The default bridge network assigns IP addresses like 172.17.0.x.

🔀 Workflow

advanced

Connecting two containers on a user-defined network

You want two containers, app1 and app2, to communicate securely. Which sequence of commands correctly creates a user-defined network and runs both containers attached to it?

A 3,2,1

B 1,2,3

C 1,3,2

D 2,1,3

💡 Hint

Create the network first, then run containers attached to it.

You must create the network before running containers that use it. Then run containers specifying the network.

❓ Troubleshoot

advanced

Diagnosing container communication failure

Two containers on the same user-defined network cannot ping each other by container name. What is the most likely cause?

A The containers are running on different Docker hosts without overlay network.

B The containers are using the default bridge network which supports automatic DNS resolution.

C The containers have no IP addresses assigned.

D The containers are not attached to the same user-defined network.

💡 Hint

Think about multi-host container networking and DNS resolution.

Containers on different hosts need an overlay network to communicate by name. Without it, DNS resolution fails.

✅ Best Practice

expert

Choosing the right Docker network driver for microservices

For a microservices app deployed on multiple Docker hosts, which network driver is best to enable secure, scalable container communication?

A bridge

B host

C overlay

D none

💡 Hint

Consider multi-host networking and service discovery.

The overlay driver allows containers on different hosts to communicate securely and supports service discovery, ideal for microservices.