0
0
Dockerdevops~5 mins

Host networking mode in Docker - Commands & Configuration

Choose your learning style9 modes available
LearnWhyDeepVisualTryChallengeProjectRecallTime
Introduction
Sometimes, you want a container to use the host computer's network directly. Host networking mode lets a container share the host's network, so it acts like it is running on the host itself. This helps when you need fast network access or want to avoid network isolation.
When you want a container to listen on the same network interfaces as the host without extra setup.
When running a network tool inside a container that needs to see all network traffic on the host.
When you want to avoid port mapping and let the container use host ports directly.
When you need the container to have the same IP address as the host for communication.
When performance is critical and you want to skip Docker's network translation layers.
Commands
This command runs an Nginx web server container using the host's network. The container shares the host's network stack, so it uses the host's IP and ports directly. The --rm flag removes the container after it stops.
Terminal
docker run --rm --network host nginx
Expected OutputExpected
No output (command runs silently)
→
--network host - Use the host's network stack instead of Docker's default network.
→
--rm - Automatically remove the container when it exits.
This command tests if the Nginx server is reachable on the host's localhost address. Since the container uses host networking, the server listens on the host's IP and ports.
Terminal
curl http://localhost
Expected OutputExpected
<!DOCTYPE html> <html> <head> <title>Welcome to nginx!</title> </head> <body> <h1>Welcome to nginx!</h1> </body> </html>
This command lists running containers to verify the Nginx container is running with host networking.
Terminal
docker ps
Expected OutputExpected
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES abcdef123456 nginx "/docker-entrypoint.…" 10 seconds ago Up 10 seconds loving_morse
Key Concept

If you remember nothing else from this pattern, remember: host networking mode lets a container share the host's network directly, removing network isolation.

Common Mistakes
Trying to use port mapping (-p) with host networking mode.
Port mapping does not work with host networking because the container uses the host's network directly.
Do not use -p flags when using --network host; the container already uses host ports.
Assuming the container has its own IP address when using host networking.
The container shares the host's IP, so it does not have a separate IP address.
Access the container services via the host's IP or localhost.
Summary
Run containers with --network host to share the host's network stack.
Host networking removes network isolation and port mapping is not needed.
Use host networking for performance or when the container needs direct access to host network interfaces.