Docker Networking

Status: draft · Confidence: low (0.43) · Basis: verified_sources

Quality notes: generic_source_homepage, no_verified_sources, partial_source_verification

## TL;DR

Docker networking provides container connectivity. Drivers: bridge (default, containers on same host), host (container shares host network), overlay (multi-host, Swarm), macvlan (container gets MAC address, appears as physical device), none (isolated). Custom networks enable DNS-based service discovery.

## Core Explanation

Bridge: Docker creates docker0 bridge, containers get IP from 172.17.0.0/16 subnet. `--link` (deprecated) vs. user-defined networks (DNS resolution: container names resolve). Overlay: VXLAN encapsulation across hosts. Port mapping: `-p 8080:80` maps host 8080 to container 80. Network isolation: containers on different networks can't communicate (unless explicitly connected).

## Further Reading

- [Docker Networking Documentation](undefined)

## Related Articles

- [Networking Skills](../../business/networking-skills.md)
- [Docker Compose](../docker-compose.md)
- [Docker Security Best Practices](../docker-security-best-practices.md)