Connecting containers to multiple networks in Docker - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the command to connect an existing Docker container to a new network?

Use docker network connect <network-name> <container-name> to connect a running or stopped container to an additional network.

intermediate

How can a Docker container be connected to multiple networks at creation?

Use the --network flag for the first network and then connect additional networks using docker network connect after the container is created.

beginner

What happens if a container is connected to multiple Docker networks?

The container can communicate with other containers on all connected networks, each network providing a separate IP address inside the container.

beginner

How to list all networks a Docker container is connected to?

Run docker inspect <container-name> and look under the Networks section in the output.

intermediate

Can a container be disconnected from a Docker network? If yes, how?

Yes, use docker network disconnect <network-name> <container-name> to remove a container from a network.

Which command connects a running container named 'webapp' to a network called 'frontend'?

A docker network connect frontend webapp

B docker connect network webapp frontend

C docker container connect webapp frontend

D docker network attach webapp frontend

The correct syntax is docker network connect <network> <container>.

What is true about a container connected to multiple Docker networks?

A It can only communicate on the first network.

B It merges all networks into one.

C It loses connectivity on all networks except the last connected.

D It has multiple IP addresses, one per network.

Each network assigns its own IP address to the container, allowing communication on all connected networks.

How do you check which networks a container is connected to?

A docker inspect <container> and check the Networks section

B docker network list --container <container>

C docker container networks <container>

D docker network show <container>

The docker inspect command shows detailed info including connected networks.

Can you connect a container to a network after it has started?

A Only if the container is restarted

B Yes, using docker network connect

C Only if the container is stopped

D No, networks must be set at creation

Docker allows connecting running containers to additional networks anytime.

What command removes a container from a Docker network?

A docker container disconnect <container> <network>

B docker network remove <container>

C docker network disconnect <network> <container>

D docker network detach <network> <container>

The correct command is docker network disconnect with network and container names.

Explain how to connect a Docker container to multiple networks and why this might be useful.

Think about how containers can talk on different networks and how to add networks after creation.

Describe the steps to verify and manage network connections of a Docker container.

Focus on commands to view and change network connections.

Practice

1. What is the main benefit of connecting a Docker container to multiple networks?

easy

A. It increases the container's CPU usage automatically.

B. It makes the container run faster by using multiple networks.

C. It allows the container to communicate with different isolated groups of containers.

D. It automatically backs up container data across networks.

Solution

1. Step 1: Understand Docker networks

   Docker networks isolate groups of containers so they can communicate securely within the group.

2. Step 2: Multiple networks allow multi-group communication

   Connecting a container to multiple networks lets it talk to containers in each network separately.

3. Final Answer:

   It allows the container to communicate with different isolated groups of containers. -> Option C

4. Quick Check:

   Multiple networks = multi-group communication [OK]

Hint: Multiple networks let containers talk to separate groups [OK]

Common Mistakes:

• Thinking multiple networks speed up container
• Assuming multiple networks backup data
• Believing CPU usage increases automatically

2. Which Docker command correctly connects an existing container named webapp to a network called frontend?

easy

A. docker network add webapp frontend

B. docker connect network webapp frontend

C. docker container network add webapp frontend

D. docker network connect frontend webapp

Solution

1. Step 1: Recall Docker network connect syntax

   The correct syntax is docker network connect [network] [container].

2. Step 2: Match command to syntax

   docker network connect frontend webapp matches the syntax exactly: docker network connect frontend webapp.

3. Final Answer:

   docker network connect frontend webapp -> Option D

4. Quick Check:

   docker network connect = correct syntax [OK]

Hint: Use 'docker network connect [network] [container]' syntax [OK]

Common Mistakes:

• Swapping network and container order
• Using 'docker connect network' which is invalid
• Trying to add network with 'docker network add'

3. Given the commands below, what networks will the container db be connected to?

docker network create backend
docker network create monitoring

docker run -d --name db --network backend postgres

docker network connect monitoring db

medium

A. Only backend

B. Both backend and monitoring

C. Only monitoring

D. No networks connected

Solution

1. Step 1: Analyze initial container network

   The container db is started with --network backend, so it connects to backend first.

2. Step 2: Analyze network connect command

   The command docker network connect monitoring db adds monitoring network to the same container.

3. Final Answer:

   Both backend and monitoring -> Option B

4. Quick Check:

   Initial network + connect command = multiple networks [OK]

Hint: Initial network + connect command = multiple networks [OK]

Common Mistakes:

• Assuming second connect replaces first network
• Thinking container can only have one network
• Ignoring the network connect command

4. You tried to connect a container app to a network frontend using docker network connect frontend app, but got an error: Error response from daemon: network frontend not found. What is the most likely cause?

medium

A. The network frontend does not exist.

B. The container app is not running.

C. You used the wrong command syntax.

D. Docker daemon is not running.

Solution

1. Step 1: Understand the error message

   The error says network frontend not found, meaning Docker cannot find a network named frontend.

2. Step 2: Check possible causes

   If the network does not exist, the connect command fails. Container running state or syntax errors produce different messages.

3. Final Answer:

   The network frontend does not exist. -> Option A

4. Quick Check:

   Error 'network not found' = missing network [OK]

Hint: Check network existence if 'network not found' error appears [OK]

Common Mistakes:

• Assuming container must be running for connect
• Blaming command syntax without checking network
• Ignoring Docker daemon status

5. You have two networks: frontend and backend. You want a container api to be initially connected to frontend and communicate with containers in both networks but keep traffic isolated. Which sequence of commands correctly sets this up?

hard

A. docker network create frontend

docker network create backend

docker run -d --name api --network frontend myapi

docker network connect backend api

B. docker network create frontend

docker network create backend

docker run -d --name api --network backend myapi

docker network connect frontend api

C. docker network create frontend

docker network create backend

docker run -d --name api myapi

docker network connect frontend api

docker network connect backend api

D. docker network create frontend

docker network create backend

docker run -d --name api --network frontend --network backend myapi

Solution

1. Step 1: Create both networks

   Commands docker network create frontend and docker network create backend create the two isolated networks.

2. Step 2: Start container on one network and connect to the other

   Start api on frontend network, then connect it to backend using docker network connect backend api. This keeps traffic isolated but allows communication on both.

3. Final Answer:

   docker network create frontend docker network create backend docker run -d --name api --network frontend myapi docker network connect backend api -> Option A

4. Quick Check:

   Start on one network + connect second = multiple isolated networks [OK]

Hint: Start container on one network, then connect to others [OK]

Common Mistakes:

• Trying to specify two --network flags in docker run
• Not connecting container to second network after start
• Starting container without any network