![docker network performance docker network performance](https://d1jnx9ba8s6j9r.cloudfront.net/blog/wp-content/uploads/2018/07/goals.png)
- #Docker network performance how to
- #Docker network performance drivers
- #Docker network performance driver
#Docker network performance how to
![docker network performance docker network performance](https://community.cisco.com/legacyfs/online/fusion/92688_Untitled1.png)
![docker network performance docker network performance](http://techtraits.com/assets/images/docker-net-tcp.png)
You can have two different VMs running locally, or use a couple VPS with static IPs. Two Linux hosts with Docker installed and running on each of them. Regardless of the VMs running them or the VM’s own network configuration. The overlay network is “overlaid” on top of the VM and containers will get IP address like 10.0.0.2, 10.0.0.3, etc on this network. The two VMs are running docker, with containers attached to overlay network. As though they are part of the same network. The essential point is, if there are two hosts, each running Docker, then the Overlay network helps create a subnet which is overlaid on top of these two hosts and each Docker container connected to this overlay network can communicate with every other container using their own block of IP address, subnet and default gateway. These networks could be private ones, or even public infrastructure on Cloud.
#Docker network performance driver
Overlay driver is designed to facilitate communication between docker containers that are hidden from each other in entirely different networks. Let’s have a closer look at what Overlay driver helps us accomplish and how we can create one for ourselves and attach containers to it.
#Docker network performance drivers
However, there are other drivers available as well, such as macvlan and Overlay driver, which is the topic of this post. This is the default network to which every container will try and connect, unless specified otherwise. For example, if you run docker network ls you will see a network named bridge, this driver uses bridge networking driver. Network adapters are also initialized using these drivers, carrying the same exact name. Docker comes with three networking drivers by default.