Docker Networking on Software Gone Wild
A year and a half ago, Docker networking couldn’t span multiple hosts and used NAT with port mapping to expose container-based services to the outside world.
Docker is the hottest Linux container solution these days. Want to know more about it? Matt Oswalt is running Introduction to Docker webinar in a few days.
In August 2014 a small startup decided to change all that. Docker bought them before they managed to get public, and the rest is history.
As expected, the SocketPlane team was extremely busy – it took us almost a year before all the stars aligned and we managed to record a deep dive into next-generation Docker networking.
The most interesting part (for me): the same team worked on an OpenDaylight-based controller solution before started SocketPlane, and decided to use a fully-distributed control plane in their next product instead of a centralized control-plane solution. Another data point supporting my claim that centralized control plane (as opposed to centralized control) works best in marketing whitepapers.
For the rest of the story, listen to Episode 49 of Software Gone Wild, and make sure you stay till the very end where we started discussing running multi-realm Minecraft on a Docker swarm as well as managing a Docker cluster from a Minecraft client.
More information
- Sample Multi-Host and Swarm Environments
- Multi-realm Minecraft demo
- The voting app Dave mentioned
To reach the guests on Twitter, use these handles:
- Brent Salisbury: @networkstatic
- Dave Tucker: @dave_tucker
- Madhu Venugopal: @MadhuVenugopal
Oh, and don’t forget to register for the webinar after listening to the podcast ;)
https://github.com/DonMills/dockeroverlayvagrant
A multi node environment using etcd as the key/value store
https://github.com/DonMills/dockeroverlayvyos
A similar setup but with multiple networks and a vyos router in the middle to test layer 3
Enjoy...