Docker secures the network by managing rules that block connectivity between different Docker networks.īehind the scenes, the Docker Engine creates the necessary Linux bridges, internal interfaces, iptables rules, and host routes to make this connectivity possible. External access is granted by exposing ports to containers.
Docker network inside outside driver#
The bridge driver creates a private network internal to the host so containers on this network can communicate. It’s simple to understand, simple to use, and simple to troubleshoot, which makes it a good networking choice for developers and those new to Docker. The bridge networking driver is the first driver on our list. For a more in depth comparison and discussion of even more network drivers, check out the Docker Network Reference Architecture. Together they cover a very broad list of networking use cases and environments.
Docker network inside outside drivers#
The most commonly used built-in network drivers are bridge, overlay and macvlan. There are built-in network drivers that come included with Docker Engine and there are also plug-in network drivers offered by networking vendors and the community.
Naturally, the next question is which network driver should I use ? Each driver offers tradeoffs and has different advantages depending on the use case. These are pluggable interfaces for the Docker Engine, Swarm, and UCP that provide special capabilities like multi-host networking, network layer encryption, and service discovery. The result is portability and it comes from CNM’s powerful network drivers.
It’s CNM that brokers connectivity for your Docker containers and also what abstracts away the diversity and complexity so common in networking. In between applications and the network sits Docker networking, affectionately called the Container Network Model or CNM. Applications requirements and networking environments are diverse and sometimes opposing forces.
0 kommentar(er)
