For questions about the network configuration of the docker service or of the containers running in it.
The Docker paravirtualization engine has multiple models to configure the network access of the containers:
- bridge: in other virtualization engines, this is called as "NAT network". What other virtualization engines call "bridged network", is called "macvlan" in the docker terminology (see below). The docker containers are on a virtual local network (172.17.0.0/16), their external connections are NAT-ted to the local network address of the host machine.
- host: The containers use the same network interface as the host. This has the side-effect that they multiple services can not bind to the same ports simultaneously.
- overlay: essentially a shared bridged network among multiple docker hosts of a docker swarm.
- macvlan: in other virtualization engines, this is called "bridged network". The docker host creates a virtual "clone" of a host network interface, with an alternate MAC address, and binds it to the containers. The containers will be seen on the local network of the host, as if they would be entirely different machines (with their separate MAC and IP addressing).
- none: the container has no access to any network.
- there is also an option to develop custom network plugins.