Multi-Host Docker Networking is now ready for production

At DockerCon in June, we first introduced experimental support for Docker Networking. In Docker 1.9, we are excited to announce that Networking is ready to use in production and works with Swarm and Compose. Networking is a feature of Docker Engine that allows you to create virtual networks and attach containers to them so you can create the network topology that is right for your application. The networked containers can even span multiple hosts, so you don’t have to worry about what host your container lands on. They seamlessly communicate with each other wherever they are – thus enabling true distributed applications.

Networking Receives an Upgrade

After our initial progress report, we are excited to announce a new networking system for Docker Engine. Containers can now communicate with each across hosts and configuring networking has been made much more flexible. What’s more, this functionality is entirely pluggable with networking drivers, so you can choose a networking system that best suits your infrastructure without locking your app into any particular system.   How it works You can now create a network and attach containers to it. This can be useful for segmenting your containers, applying policies or even just for keeping your containers organised. docker network create foo docker run -itd – debian:latest How do you use your networks? Please let us know by joining the discussion on #docker-network on Freenode.

Docker Networking takes a step in the right direction

It’s been just over one month since the SocketPlane team joined Docker and we’ve been working hard to deliver on our promise of helping to grow a healthy ecosystem around Networking. This week, with the help of our partners, we’ve taken the first major step by making libnetwork open source. What is libnetwork? In its initial form libnetwork is an amalgamation of the networking code from both libcontainer and Docker Engine that we expect to grow into a multi-platform library for networking containers, much like how libcontainer is used to create containers today. Libnetwork also introduces the Container Network Model (CNM) which was inspired by this GitHub issue and the valuable input from networking partners Cisco, IBM, Joyent, Microsoft, Rancher, VMware and Weave. With the help of our ecosystem, we’ve laid the foundations for a valuable library that can be Continue reading…