Container to Host Machine Communication

Welcome back! In the previous lesson, we explored how Docker containers communicate with external services, such as the internet. Now, we're going to take a closer look at how containers can communicate directly with the host machine. This capability is crucial in real-world applications where a container might need to access resources running directly on the host. By the end of this lesson, you'll understand how to establish this communication line and verify its success.

By default, a Docker container can communicate with the host machine through its network interfaces. However, without specific configurations, this communication can be cumbersome, especially if the host's IP address changes. To streamline and simplify this process, we configure a custom host entry using the --add-host option when starting a Docker container. This defines how the container's DNS system maps a specific hostname to an IP address, essentially creating a custom DNS entry inside the container.

Here’s the command structure:

# Run a Docker container with a custom host entry
docker run --add-host <hostname>:<ip-address> <image>

• <hostname>: This is the alias or name that the container will use to refer to the host machine. For example, host.docker.internal is a Docker-provided alias that represents the host machine.

• <ip-address>: This is the IP address that the hostname maps to. Using host-gateway allows Docker to automatically resolve this to the host machine's network gateway IP, providing a direct communication path to the host.

This configuration is particularly useful in networking setups where containers need to access services running on your host machine.

Let's apply what we've learned with a straightforward command to set up communication between a Docker container and the host machine:

# Run an Alpine container and map a custom host entry to the host machine
docker run --add-host host.docker.internal:host-gateway -it alpine

Here's a breakdown:

• host.docker.internal: In this example, we're using host.docker.internal as the alias, which is a special hostname provided by Docker as a convenient alias for containers to reference and communicate with the host machine. However, you can replace this with any custom alias of your choice.

• host-gateway: This is a special Docker feature that resolves to the internal network gateway IP. It connects your Docker environment to the host's network, simplifying the connection process between the container and the host machine.

In this example, the -it option is used to run the container interactively with a terminal session, making it easier for us to test the connection from inside the container.