Practical Design Patterns in Docker Networking

Migrating an application to Docker creates an opportunity to utilize new networking topologies and features, which can provide new functionality to an existing application. This talk will provide an overview of Docker networking with a focus on the architectural choices when migrating applications. Taking sample applications we will look at the existing networking topology and cover the options available to create a simple migration and provide additional functionality.

[vicentedeluca]

True Network Engineers would be unhappy if you're relying on overlay and NAT, as you lose performance, visibility and breaks end to end IP connectivity. IP per containers brings operational overhead, which can be resolved with software and best practices. But using overlay brings IP Packets overhead, which will impact your performance (no matter hardware offload). NAT will complicate troubleshooting when you trace a request origin down to a server with 200 containers... which one made that request ? and others down falls. as a network dude I always advocate for IP per container in production workloads.

[anisht]

Which network driver do I need to opt, if I want to access the service in a container from my LAN. The docker host has two ethernet interfaces, one is configured with LAN IP addr. The other one is connected to internet, but not configured with any IP addr. The internet facing interface of the host need to be bridged to the container, which needs to be configured with internet ip addr. So that the container can speak to internet but not with LAN, and I can access the service via browser from LAN.

[madhukarnaidugunda]

nice one .Can please share the slides please ?

[wtc]

Willkommen im Schnakerparadies mit PowerPoint-Karaoke was für ein unbrauchbares Video.