This option isn’t often used, because typical container use cases involve a desire to keep workloads running in containers isolated from each other. That means that applications running within the container have full access to all network interfaces and traffic on the hosting server itself. There are three options I would recommend every network engineer to be familiar with: host, bridge, and none.Ĭontainers attached to a network using the host driver run without any network isolation from the underlying host that is running the container.
These options are available in the form of different network drivers that are included with Docker itself or added as a networking plugin.
What does “default Docker networking” mean, exactly?īefore I jump right into the technical bits, I wanted to define exactly what I mean by “default Docker networking.” Docker offers engineers many options for setting up networking. If there is interest in learning more about the topic, I’d be happy to continue and explore other aspects of Docker networking in future posts.
As I considered possible choices for where to spend time, I figured that exploring the default Docker networking behavior and setup was a great place to start. I’d need to scope the content down to make it blog-sized. I knew as soon as I decided on container networking for my next topic that there is far too much material to cover in a single blog post. Specifically, Docker container networking. Following up on my last blog post where I explored the basics of the Linux ‘ip’ command, I’m back with a topic that I’ve found both interesting and a source of confusion for many people: container networking.
0 kommentar(er)
