Host Docker Internal in Linux

Isaac Tony Mar 11, 2025 Docker Docker Linux

Understanding host.docker.internal
Setting Up host.docker.internal in Linux
Testing the Configuration
Conclusion
FAQ

In the world of containerization, Docker has emerged as a leading platform, enabling developers to create, deploy, and manage applications seamlessly. However, one common challenge that users face, especially on Linux, is accessing services running inside Docker containers from the host machine. Enter host.docker.internal—a special DNS name that allows your Docker containers to communicate with the host.

In this tutorial, we will explore how to effectively use host.docker.internal in Linux, providing you with clear examples and explanations to enhance your understanding. Whether you’re a seasoned developer or just starting with Docker, this guide will help you navigate the complexities of container networking with ease.

Understanding host.docker.internal

Before diving into the implementation, it’s essential to grasp what host.docker.internal is and why it matters. This DNS name serves as a bridge between your Docker containers and the host machine, allowing for smoother communication. Unlike Windows and Mac, where this feature is built-in, Linux users need to set it up manually. This capability is particularly useful when you want to access services like databases, APIs, or any other applications running on your host from within a Docker container.

Setting Up host.docker.internal in Linux

To enable host.docker.internal on Linux, you need to create a network alias that points to the host’s IP address. This process involves a few straightforward steps. Let’s walk through the setup.

Step 1: Determine Your Host IP Address

First, you need to identify the IP address of your host machine. You can do this by running the following command in your terminal:

hostname -I | awk '{print $1}'

Output:

192.168.1.100

In this example, 192.168.1.100 is the host’s IP address. Make sure to note this down as you will use it in the next steps.

Step 2: Create a Docker Network

Next, create a new Docker network where you will define the alias. Use the following command:

docker network create --subnet=192.168.1.0/24 my_network

Output:

my_network

This command creates a new Docker network called my_network with a specified subnet. Adjust the subnet according to your network configuration.

Step 3: Run Your Container with the Network Alias

Now, you can run a Docker container on this network and set the alias to host.docker.internal:

docker run --rm -it --network my_network --add-host=host.docker.internal:192.168.1.100 alpine /bin/sh

Output:

/ #

This command launches an Alpine Linux container, adds the host’s IP as host.docker.internal, and opens a shell for you to interact with.

Now that you have set up host.docker.internal, you can access services on your host machine from within your Docker container using this alias.

Testing the Configuration

To ensure that everything is working correctly, you can test the connection from within your container. Here’s how to do it:

Step 1: Start a Simple HTTP Server on the Host

On your host machine, start a simple HTTP server using Python:

python3 -m http.server 8000

Output:

Serving HTTP on 0.0.0.0 port 8000 (http://0.0.0.0:8000/) ...

This command starts an HTTP server that listens on port 8000.

Step 2: Access the Server from the Container

Now, go back to your Docker container and use curl to access the server:

curl http://host.docker.internal:8000

Output:

<!doctype html>
<html>
<head>
    <title>Directory listing</title>
</head>
<body>
<h1>Directory listing</h1>
</body>
</html>

This output confirms that your container can successfully communicate with the host using host.docker.internal.

Conclusion

Using host.docker.internal in Linux is a straightforward process that can significantly enhance your development workflow. By following the steps outlined in this guide, you can seamlessly connect your Docker containers to services running on your host machine. Whether you’re developing applications or testing APIs, this setup will streamline your processes and improve productivity. Embrace the power of Docker and take your containerization skills to the next level!

FAQ

What is host.docker.internal?
host.docker.internal is a special DNS name that allows Docker containers to communicate with the host machine.
How do I find my host machine’s IP address?
You can find your host machine’s IP address by running the command hostname -I | awk '{print $1}'.
Can I use host.docker.internal on all operating systems?
While host.docker.internal is natively supported on Windows and Mac, Linux users need to set it up manually.
What is the purpose of creating a Docker network?
Creating a Docker network allows you to define custom networking configurations and manage container communication more effectively.

How can I test the connection between my container and host?
You can test the connection by running a service on your host and accessing it from within your Docker container using curl.

Enjoying our tutorials? Subscribe to DelftStack on YouTube to support us in creating more high-quality video guides. Subscribe

Author: Isaac Tony

Isaac Tony is a professional software developer and technical writer fascinated by Tech and productivity. He helps large technical organizations communicate their message clearly through writing.