Docker

Networks Commands

Connect containers and manage network isolation. Learn Docker's network drivers, DNS resolution, and how to design secure, scalable network architectures for containerized applications.

10 commands

Pro Tips

Create custom bridge networks - containers can reach each other by name, unlike the default bridge.

Use 'docker network inspect' to see which containers are connected and their IP addresses.

For containers that need host network access without NAT, use '--network host' (Linux only).

Common Mistakes

The default bridge network doesn't provide automatic DNS resolution between containers. Use custom networks.

Exposing ports with -p makes them accessible from outside. Only expose what's necessary for security.

Commands

List networks

$ docker network ls

Show all Docker networks.

Create network

$ docker network create <network-name>

Create a bridge network.

Create network with subnet

$ docker network create --subnet=172.18.0.0/16 <network>

Create network with custom subnet.

Inspect network

$ docker network inspect <network>

Show network details and connected containers.

Connect container to network

$ docker network connect <network> <container>

Connect running container to network.

Disconnect from network

$ docker network disconnect <network> <container>

Disconnect container from network.

Remove network

$ docker network rm <network>

Remove a network.

Remove unused networks

$ docker network prune

Remove all unused networks.

Run with network

$ docker run --network=<network> <image>

Run container on specific network.

Run with host network

$ docker run --network=host <image>

Use host's network stack directly.