You can get list of default Docker network drivers with the docker network ls command: As mentioned in the introduction, the Docker bridge network driver relies on the Linux bridge network.ĭocker0 is Linux bridge network with default network range – 172.17.0.1/16. When we run the container, the default network used by Docker is the bridge network. All drivers have local scope except the overlay driver that works in cluster (swarm) mode. Network drivers that come with the Docker installation are: bridge, host, MACVLAN, none and overlay. Docker network drivers use iptables to segment network traffic, port mapping, traffic markup and load balancing. Iptables (built-in mechanism in the Linux kernel that allows packet filtering and the 元/4 firewall.Docker drivers use virtual adapters to connect containers on the same Linux Bridge) Represent a link between network namespaces. Virtual Ethernet adapters (represent network sockets on the container side and Linux Bridge.Network namespace (isolated network space used by each container with its own interfaces, routes and firewall rules).Linux bridge (L2 virtual switch built into the Linux kernel that does the job like a physical switch).At a low level, the Docker network is actually a Linux network because it uses all the capabilities of the Linux kernel to achieve its goals: The physical layer of the network does not need to be specifically configured. Docker network drivers are a high level presentation of networking capabilities. There are various drivers but the default drivers that come with the Docker have local or cluster (swarm) scope. Docker enables it by deploying its native and third-party network drivers. Access to containers within the same and external networkĭocker network architecture covers all network scenarios required for successful communication at the local, remote or cluster level.