Why container networking matters in Docker - Why It Works

Introduction

Containers run applications in isolated environments. Networking connects these containers so they can talk to each other and the outside world. Without networking, containers would be isolated and unable to share data or services.

When you want your web app container to communicate with a database container on the same host.

When you need to expose a containerized service to users outside your server.

When multiple containers need to work together as parts of a bigger application.

When you want to control which containers can access each other for security.

When you want to assign fixed IP addresses or hostnames to containers for easier management.

Commands

This command creates a new user-defined network called 'my-network' so containers can connect and communicate on it.

Terminal

docker network create my-network

Expected Output

my-network

Runs a PostgreSQL database container named 'db' attached to 'my-network' so it can communicate with other containers on the same network.

Terminal

docker run -d --name db --network my-network postgres:15

Expected Output

a1b2c3d4e5f6g7h8i9j0k1l2m3n4o5p6q7r8s9t0u1v2w3x4y5z6a7b8c9d0e1f2

→

--network - Connects the container to the specified network

→

-d - Runs the container in detached mode (in the background)

Runs an Nginx web server container named 'web' on 'my-network' and maps port 8080 on the host to port 80 in the container, making it accessible from outside.

Terminal

docker run -d --name web --network my-network -p 8080:80 nginx:1.25

Expected Output

f1e2d3c4b5a697887766554433221100ffeeddccbbaa99887766554433221100

→

--network - Connects the container to the specified network

→

-p - Publishes container port to the host

→

-d - Runs the container in detached mode

Shows details about 'my-network', including connected containers and their IP addresses, helping verify network setup.

Terminal

docker network inspect my-network

Expected Output

[

    {

        "Name": "my-network",

        "Id": "e1f2d3c4b5a697887766554433221100ffeeddccbbaa99887766554433221100",

        "Created": "2024-06-01T12:00:00.000000000Z",

        "Scope": "local",

        "Driver": "bridge",

        "EnableIPv6": false,

        "IPAM": {

            "Driver": "default",

            "Config": [

                {

                    "Subnet": "172.18.0.0/16",

                    "Gateway": "172.18.0.1"

                }

            ]

        },

        "Containers": {

            "a1b2c3d4e5f6g7h8i9j0k1l2m3n4o5p6q7r8s9t0u1v2w3x4y5z6a7b8c9d0e1f2": {

                "Name": "db",

                "EndpointID": "1234567890abcdef",

                "MacAddress": "02:42:ac:12:00:02",

                "IPv4Address": "172.18.0.2/16",

                "IPv6Address": ""

            },

            "f1e2d3c4b5a697887766554433221100ffeeddccbbaa99887766554433221100": {

                "Name": "web",

                "EndpointID": "abcdef1234567890",

                "MacAddress": "02:42:ac:12:00:03",

                "IPv4Address": "172.18.0.3/16",

                "IPv6Address": ""

            }

        },

        "Options": {},

        "Labels": {}

    }

]

Key Concept

Containers need networks to communicate with each other and the outside world, making container networking essential for multi-container apps and external access.

Common Mistakes

Running containers without specifying a user-defined network and expecting them to communicate.

By default, containers on the default bridge network cannot resolve each other by name, causing communication failures.

Create and use a user-defined network so containers can find each other by name and communicate easily.

Not publishing container ports to the host when external access is needed.

Without port mapping, services inside containers are not reachable from outside the host machine.

Use the -p flag to map container ports to host ports for external access.

Assuming containers on different networks can communicate without extra setup.

Docker isolates networks; containers on separate networks cannot talk unless connected to both or bridged.

Connect containers to the same network or configure network bridging to enable communication.

Summary

Create a user-defined Docker network to allow containers to communicate by name.

Run containers attached to this network so they can find and talk to each other.

Publish container ports to the host to allow external access to container services.

Inspect the network to verify which containers are connected and their IP addresses.

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