Announcing Compose 1.3, Swarm 0.3 and Machine 0.3

As with the last update to Compose, Swarm and Machine, we’re releasing versions alongside the new version of Engine at DockerCon 2015. In all three projects we’ve made some big steps towards production readiness, stability, and new integrations such as Mesos support in Swarm.

SocketPlane Excited to Be Joining Docker to Collaborate with Networking Ecosystem

At Socketplane we started out as four guys with a collectively strong belief in open source and open communities.  We aligned around a shared vision that we wanted to be a critical part of Docker’s once in a decade disruption. Now that we are part of the Docker team, we couldn’t be happier.     We never looked to hedge our bets, our success was and obviously still is tied to the success of Docker. While there are many reasons that we decided to join the team, first and foremost Docker is unlike any other projects we have worked on in the past; the focus on user experience and simplicity is unmatched.  Our early work with Docker during the open network design sprints gave us clear indications that the Docker maintainers were interested in being good open source stewards for Continue reading…

Victor Coisne

DockerCon EU Breakouts from Day 2

Following yesterday’s post on the breakout session videos from day 1, here are some more amazing clips from the 2nd day of DockerCon Europe. This post covers several orchestration and container management technologies such as Consul, Mesos and Clocker as well as user stories from Shopify and Weeby.co. Orchestrating Docker with Terraform and Consul by Michel hashimoto

Jérôme Petazzoni

Unionize: network superpowers for your docker containers

Some people asked for special network setups with docker containers: Bryan Berry wants to run Cassandra nodes and specify their IP addresses [1]; Matt Parlane wants to expose arbitrary IP addresses to docker containers [2]; Jeremy Grosser wants to plumb docker containers with openvswitch; I personally want to play with doozerd[3], but it requires UDP, which is not yet available in docker. Generally speaking, specifying IP addresses for containers obviously leads to setups which are not reproducible. But it is also obviously very useful for many test setups. To encourage people to use docker in those scenarios (rather than switching to plain LXC!), let me introduce: unionize[4]. Unionize: is a simple bash script, using basic tools (brctl, ip, ifconfig) lets you create private networks for your containers lets you connect containers with the outside world, in arbitrary topologies. Sample use: Continue reading…

Get the Latest Docker News by Email

Docker Weekly is a newsletter with the latest content on Docker and the agenda for the upcoming weeks.

Solomon Hykes

Docker 0.2.0: stability, full interactive mode, community layers, better networking

Hi everyone, Exactly one month after our first release, I am very excited to announce Docker version 0.2.0. The primary focus of this release is stability, but it also packs several cool new features. Before diving in, let me just say that the volume and quality of contributions we’ve received – bug reports, feedback, advice, pull requests – has blown my mind. I can’t thank you enough for your help, people. Now let’s make sure Docker lives up to your expectations! CONTENTS ========= * 0.2.0 Summary * Stability * Full interactive mode * Community layers * Static port allocation * Access ports on localhost * What’s next * Searchable index * Open-source registry * Data volumes * Remote API * Runtime API * Build! * How you can help * Hack day on May 2