Why container networking matters in Docker - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to list all Docker networks on your system.

Docker

docker network [1]

Drag options to blanks, or click blank then click option'

Arm

Bcreate

Cstart

Dls

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'create' instead of 'ls' will try to make a new network, not list existing ones.

The docker network ls command lists all networks available in Docker. This helps you see how containers can connect.

2fill in blank

medium

Complete the command to connect a running container named 'webapp' to a network called 'frontend'.

Docker

docker network connect [1] webapp

Drag options to blanks, or click blank then click option'

Abridge

Bfrontend

Cdefault

Dbackend

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'bridge' connects to the default network, not the intended 'frontend' network.

The docker network connect frontend webapp command connects the 'webapp' container to the 'frontend' network, allowing it to communicate with other containers on that network.

3fill in blank

hard

Fix the error in the command to create a new Docker network named 'mynetwork' with the bridge driver.

Docker

docker network create --driver [1] mynetwork

Drag options to blanks, or click blank then click option'

Abridge

Boverlay

Chost

Dnone

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'overlay' requires a swarm setup and won't work for simple bridge networks.

The bridge driver creates a private internal network on the host. Using --driver bridge is the correct way to create a bridge network.

4fill in blank

hard

Fill both blanks to run a container named 'db' attached to the 'backend' network and expose port 5432.

Docker

docker run -d --name db --network [1] -p [2]:5432 postgres

Drag options to blanks, or click blank then click option'

Abackend

Bfrontend

C5432

D3306

Attempts:

3 left

💡 Hint

Common Mistakes

Using port 3306 is for MySQL, not PostgreSQL.

The container runs on the 'backend' network and exposes port 5432, which is the default port for PostgreSQL.

5fill in blank

hard

Fill all three blanks to create a user-defined bridge network named 'appnet', run a container named 'app' on it, and connect another container named 'worker' to the same network.

Docker

docker network [1] appnet && docker run -d --name app --network [2] nginx && docker network [3] appnet worker

Drag options to blanks, or click blank then click option'

Acreate

Bconnect

Cdisconnect

Drm

Eappnet

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'disconnect' or 'rm' will not create or connect networks properly.

First, create the network with create. Then run the 'app' container on that network. Finally, connect the 'worker' container to 'appnet' using connect.

Practice

1. Why is container networking important in Docker?

easy

A. It allows containers to communicate and share data with each other.

B. It speeds up the container startup time.

C. It reduces the size of container images.

D. It automatically updates containers to the latest version.

Solution

1. Step 1: Understand container communication

   Containers need to talk to each other to share data and work together in an app.

2. Step 2: Recognize networking role

   Networking connects containers so they can send messages and data between them.

3. Final Answer:

   It allows containers to communicate and share data with each other. -> Option A

4. Quick Check:

   Container networking = communication [OK]

Hint: Networking connects containers to share data easily [OK]

Common Mistakes:

• Thinking networking speeds up startup
• Confusing networking with image size
• Assuming networking updates containers

2. Which Docker command correctly creates a new network named my-net?

easy

A. docker network new my-net

B. docker create network my-net

C. docker network create my-net

D. docker net create my-net

Solution

1. Step 1: Recall Docker network creation syntax

   The correct command starts with docker network create followed by the network name.

2. Step 2: Match the command to options

   Only docker network create my-net uses the correct syntax: docker network create my-net.

3. Final Answer:

   docker network create my-net -> Option C

4. Quick Check:

   Correct syntax = docker network create [OK]

Hint: Use 'docker network create' to make networks [OK]

Common Mistakes:

• Swapping 'create' and 'network' order
• Using 'new' instead of 'create'
• Shortening 'network' to 'net'

3. What will happen if you run docker run --network my-net nginx assuming my-net exists?

medium

A. The nginx container will connect to the my-net network and be able to communicate with other containers on it.

B. The container will fail to start because my-net is not a valid network.

C. The container will start but will not be connected to any network.

D. The container will connect to the default bridge network instead.

Solution

1. Step 1: Understand the --network flag

   The --network option connects the container to the specified network if it exists.

2. Step 2: Check network existence and effect

   Since my-net exists, the container joins it and can communicate with others on that network.

3. Final Answer:

   The nginx container will connect to the my-net network and be able to communicate with other containers on it. -> Option A

4. Quick Check:

   --network connects container to specified network [OK]

Hint: Use --network to join existing networks [OK]

Common Mistakes:

• Assuming container fails if network exists
• Thinking container starts without network
• Believing default network is used when specified

4. You tried to connect a container to a network using docker run --network my-net nginx but got an error: network my-net not found. What is the likely cause?

medium

A. The container name conflicts with the network name.

B. The nginx image is incompatible with custom networks.

C. The Docker daemon is not running.

D. The network my-net was not created before running the container.

Solution

1. Step 1: Analyze the error message

   The error says network my-net not found, meaning Docker can't find that network.

2. Step 2: Identify common causes

   This usually happens if the network was never created or was deleted before running the container.

3. Final Answer:

   The network my-net was not created before running the container. -> Option D

4. Quick Check:

   Network must exist before use [OK]

Hint: Create network before using it with containers [OK]

Common Mistakes:

• Blaming image compatibility
• Assuming Docker daemon stopped
• Confusing container and network names

5. You have two containers: a web app and a database. You want the web app to access the database securely without exposing the database port to the outside. Which Docker networking approach should you use?

hard

A. Use the host network mode for both containers.

B. Create a user-defined bridge network and connect both containers to it.

C. Expose the database port to the host and connect the web app via localhost.

D. Run both containers without any network to isolate them.

Solution

1. Step 1: Understand secure container communication

   To keep the database private, containers should communicate on an isolated network, not exposing ports to the outside.

2. Step 2: Choose the right network type

   A user-defined bridge network allows containers to talk securely and privately without exposing ports externally.

3. Step 3: Evaluate other options

   Host mode shares the host network (less secure), exposing ports risks outside access, and no network prevents communication.

4. Final Answer:

   Create a user-defined bridge network and connect both containers to it. -> Option B

5. Quick Check:

   User-defined bridge = secure container communication [OK]

Hint: Use user-defined bridge for private container communication [OK]

Common Mistakes:

• Using host mode exposing host network
• Exposing database port publicly
• Isolating containers with no network