Network drivers

Learn bridge, host and none network drivers.

Network drivers

Docker builds container networks with drivers:

bridge (default): a virtual bridge on the host; containers get an IP on a private subnet.
host: the container uses the host's network directly; there's no isolation and no port mapping.
none: no network; loopback only.
overlay: connects several Docker hosts (Swarm).

docker run --rm --network none alpine ip addr      # only lo
docker run -d --network host nginx                 # directly on the host's port 80

When to use which?

In most cases a user-defined bridge network is the right choice (in the next lessons). The host network is chosen for applications using many ports or wanting the lowest latency, but it only fully works on Linux. none is the safest option for batch jobs that need no network at all.

docker run --rm --network none -v "$PWD":/veri alpine sha256sum /veri/arsiv.tar

Exercise Choosing a network

Write two commands: run ip addr in an alpine container that is deleted when done and has no network; start a container named web from nginx in the background on the host's network.

Show example solution

docker run --rm --network none alpine ip addr
docker run -d --name web --network host nginx

Test yourself

What does -p 8080:80 do when using --network host?
- Nothing; port mapping is ignored
- It maps 8080 to 80
- It errors and the container doesn't start
- It opens both ports
Show answer

Nothing; port mapping is ignored — The container is already on the host network; the app listens on 80 directly.

Run the container without a network.

docker run --rm --network ____ alpine ip addr

Show answer

docker run --rm --network none alpine ip addr

Match the drivers.

bridge

Default virtual bridge
host

The host's network
none

No network
overlay

Multi-host network

Next lesson: docker network ls

We Are Enhancing Your Experience

Cookie Preferences

Strictly Necessary Cookies

Analytical Cookies