Docker Deep Dive - Container Networking

Docker Deep Dive - Container Networking

Containers need to talk to each other. Sometimes they even need to talk to VMs and physicals and even the internet. On the flip side sometimes those VMs, physicals and the internet they need to talk back to containers.

To help with that we have got a bunch of container networking options.

Network Types in Docker

Bridge Network:

Sometimes we call this as single house networking.It's turned on by default.

SO you have got a host and it's running docker right. It's got a built-in network called bridge or NAT in windows.

Each container gets its own IP on the bridge network.They can all talk to each other.

But containers on seperate bridges? That's a bit of a hassle because each one of this bridges is isolated, so these two we can see are isolated layer two networks and it would be the same even if they were on the same host.

The only way to get in or out is to map ports to the host. This is ok but not very Good. So Here comes the rescue Overlay Network.

Overlay Network:

So instead of isolated bridges scoped to a single host, an overlay is a single layer-two network spanning multiple host.
And the cool thing is it doesnt matter if these are all on different networks down here.