Container to Container Communication

Welcome to this lesson on container-to-container communication using Docker. In previous lessons, you learned how containers communicate with external services, like the internet, and directly with the host machine. Building on that foundation, we will now focus on establishing communication between the containers themselves. Understanding how to set up and facilitate container communication is crucial for developing applications that consist of multiple interdependent services. By the end of this lesson, you will know how to create a Docker network and connect containers to it, allowing them to communicate seamlessly within a defined environment.

To begin, let's create a user-defined network in Docker. User-defined networks provide greater flexibility and control compared to Docker's default bridge network. They allow containers to communicate with each other using container names as hostnames, which makes linking and managing containers much simpler.

To create a network, use the following command in your terminal:

# Create a user-defined network
docker network create my_network

This command creates a network named my_network. Docker assigns a unique subnet and gateway to this network, separate from Docker’s default networks, ensuring there is no interference. By using a user-defined network, containers can resolve each other by name, enhancing ease of communication.

For more details about this command, you can visit the official Docker network create documentation.

With our network set up, let's launch two containers and connect them to my_network. We will use lightweight Alpine Linux containers for this purpose. As a reminder, we perform this step to allow containers to communicate over the created network.

Here's how to launch the first container:

# Start the first container with Alpine and connect it to the network
docker run -d --name container1 --network my_network alpine sleep infinity

This command runs an Alpine Linux container named container1 and connects it to our defined network my_network. The container is set to run indefinitely (sleep infinity) so it remains active for our communication tests.

Now, let's launch the second container with the following command:

# Start the second container with Alpine and connect it to the network
docker run -d --name container2 --network my_network alpine sleep infinity

Similarly, this creates another Alpine container named container2, also connected to my_network. Both containers are now active and connected to the same network, allowing them to engage in inter-container communication.