Connecting containers to multiple networks in Docker - Commands & Configuration

Introduction

Sometimes, a container needs to talk to different groups of containers or services separately. Connecting a container to multiple networks lets it communicate in more than one isolated space, like having different phone lines for different friends.

When you want a container to access both a frontend network and a backend database network separately.

When a container needs to connect to an internal network for secure data and an external network for public access.

When you want to isolate traffic between different parts of your application but still allow some containers to bridge them.

When testing how a container behaves in different network environments without changing its setup.

When you want to connect a container to a monitoring network and an application network at the same time.

Commands

Create the first network called frontend-net where some containers will connect.

Terminal

docker network create frontend-net

Expected Output

a1b2c3d4e5f6g7h8i9j0k1l2m3n4o5p6q7r8s9t0u1v2w3x4y5z6

Create the second network called backend-net for other containers to connect.

Terminal

docker network create backend-net

Expected Output

z9y8x7w6v5u4t3s2r1q0p9o8n7m6l5k4j3i2h1g0f9e8d7c6b5a4

Start a container named my-app connected to the frontend-net network.

Terminal

docker run -d --name my-app --network frontend-net nginx

Expected Output

3f4e5d6c7b8a9f0e1d2c3b4a5e6f7d8c9b0a1e2f3d4c5b6a7e8f9d0c1b2a3

→

-d - Run container in background (detached mode)

→

--name - Assign a name to the container

→

--network - Connect container to a specific network on start

Connect the running my-app container to the backend-net network as well.

Terminal

docker network connect backend-net my-app

Expected Output

No output (command runs silently)

Check details of frontend-net to see which containers are connected.

Terminal

docker network inspect frontend-net

Expected Output

[

  {

    "Name": "frontend-net",

    "Id": "a1b2c3d4e5f6g7h8i9j0k1l2m3n4o5p6q7r8s9t0u1v2w3x4y5z6",

    "Containers": {

      "3f4e5d6c7b8a9f0e1d2c3b4a5e6f7d8c9b0a1e2f3d4c5b6a7e8f9d0c1b2a3": {

        "Name": "my-app",

        "IPv4Address": "172.18.0.2/16"

      }

    }

  }

]

Check details of backend-net to confirm my-app is connected there too.

Terminal

docker network inspect backend-net

Expected Output

[

  {

    "Name": "backend-net",

    "Id": "z9y8x7w6v5u4t3s2r1q0p9o8n7m6l5k4j3i2h1g0f9e8d7c6b5a4",

    "Containers": {

      "3f4e5d6c7b8a9f0e1d2c3b4a5e6f7d8c9b0a1e2f3d4c5b6a7e8f9d0c1b2a3": {

        "Name": "my-app",

        "IPv4Address": "172.19.0.2/16"

      }

    }

  }

]

Key Concept

A container can join multiple networks to communicate separately in each network space.

Common Mistakes

Trying to connect a container to multiple networks only at start with --network flag.

The --network flag only connects to one network at container start; others must be added later.

Start container with one network, then use 'docker network connect' to add more networks.

Assuming container IP addresses are the same across all networks.

Each network assigns its own IP; container has different IPs per network.

Inspect each network separately to see the container's IP address in that network.

Not creating the networks before connecting containers to them.

Docker cannot connect containers to networks that do not exist.

Always create networks first using 'docker network create' before connecting containers.

Summary

Create multiple Docker networks to isolate container communication.

Start a container connected to one network using --network flag.

Use 'docker network connect' to add the container to additional networks.

Inspect networks to verify container connections and IP addresses.

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