Container networking in Computer Networks - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Container Network Isolation

Which statement best describes how container networking isolates containers from the host system?

A Containers use separate network namespaces, providing isolated network stacks distinct from the host and other containers.

B Containers share the host's network stack without any isolation, allowing direct access to all host network interfaces.

C Containers use virtual machines to isolate their network, completely separate from the host's network stack.

D Containers rely on physical network cards dedicated to each container for network isolation.

💡 Hint

Think about how containers keep their network separate but still lightweight compared to virtual machines.

Containers use network namespaces to create isolated network environments. This means each container has its own network stack, IP addresses, and routing tables separate from the host and other containers.

📋 Factual

intermediate

Default Docker Bridge Network Characteristics

What is a key characteristic of the default bridge network created by Docker for containers?

A It creates a private internal network where containers can communicate using private IPs but are isolated from the host network by default.

B It assigns containers IP addresses from the host's physical network directly.

C It disables all container-to-container communication by default.

D It requires manual configuration of IP addresses for each container.

💡 Hint

Consider how containers communicate with each other and the host when using the default network.

The default Docker bridge network creates a private subnet for containers. Containers get private IPs and can talk to each other, but they are isolated from the host's physical network unless ports are explicitly published.

🔍 Analysis

advanced

Analyzing Container Port Mapping Behavior

Given a container running a web server on port 80, which Docker command option correctly maps the container's port 80 to port 8080 on the host?

A docker run --port 8080:80 mywebserver

B docker run -p 80:8080 mywebserver

C docker run -p 8080:80 mywebserver

D docker run -P 8080:80 mywebserver

💡 Hint

Remember the syntax for Docker port mapping is hostPort:containerPort.

The correct syntax is -p hostPort:containerPort. To expose container port 80 on host port 8080, use -p 8080:80.

❓ Comparison

advanced

Comparing Container Network Drivers

Which container network driver allows containers to be directly connected to the host's network stack, sharing the host's IP address?

A bridge

B macvlan

C overlay

D host

💡 Hint

Think about which driver removes network isolation between container and host.

The host network driver makes the container use the host's network stack directly, sharing the host's IP address and ports.

❓ Reasoning

expert

Troubleshooting Container Network Connectivity

A container cannot reach an external website, but the host machine can. The container uses the default bridge network. What is the most likely cause?

A The container's CPU limits are too low, causing network delays.

B The container's DNS settings are incorrect or missing, preventing domain name resolution.

C The container is using the host network driver, which blocks external access by default.

D The container's filesystem is read-only, blocking network connections.

💡 Hint

Consider what is needed for a container to translate website names into IP addresses.

Containers on the default bridge network rely on DNS to resolve domain names. If DNS settings are missing or incorrect, the container cannot reach external websites even if the host can.