Arnaud Porterie

We are excited to introduce Docker Engine 1.11, our first release built on runC ™ and containerd ™. With this release, Docker is the first to ship a runtime based on OCI technology, demonstrating the progress the team has made since donating our industry-standard container format and runtime under the Linux Foundation in June of 2015. Over the last year, Docker has helped advance the work of the OCI to make it more readily available to more users. It started in December 2015, when we introduced containerd ™, a daemon to control runC. This was part of our effort to break out Docker into small reusable components. With…

Continue reading...
Michael Chiang

Today we’re announcing a new installer for Mac OS X and Windows called Docker Toolbox. We’ve been hearing again and again that it can be difficult to get up and started with Docker in development, particularly when you’ve got your app defined with Compose and then have to install Compose separately. With the popularity of Compose, Kitematic and Boot2Docker, we realized we needed to make all the pieces work better together.

Continue reading...
Nathan LeClaire

blog post written by Nathan LeClaire, Open Source Engineer at Docker We recently released Docker Machine 0.3.0. I am a maintainer on the project, and I want to share with you some of the goodness that we have been working hard on integrating in the months since the previous release.

Continue reading...
Ben Firshman

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.

Continue reading...
Nick Lang

TL,DR I’m a developer on the Hub team at Docker, Inc. My realm of responsibility spans three different projects: Docker Hub, Registry Hub and www.docker.com. Each of these are Django applications with their own PostgreSQL, Redis, and RabbitMQ instances. I want to be able to “start projects” from one command and not only have everything running, but also have logs, Python shells, file system monitoring, a shell at the root of each project, and git fetch –all without having to type it all myself over and over and over again. This post will describe the development environment I built to…

Continue reading...
Victor Coisne

Last week, our very own Ben Firshman led a very well attended Docker Online meetup covering the release of three new open source tools for orchestrating distributed applications: Machine, Swarm and Compose.   In addition to covering the basics of each of these projects, Ben also answered a couple of questions from attendees. As mentioned in a previous blog post, these tools are not ready for production yet, but we’d really like for you to try them out and tell us what you think. 

Continue reading...
Ben Firshman

Back in December, we announced our new tools for orchestrating distributed apps: Machine, Swarm, and Compose. Today the first versions of these tools are available to download. They’re not ready for production yet, but we’d really like for you to try them out and tell us what you think. Machine takes you from “zero-to-Docker” with a single command. It lets you easily deploy Docker Engines on your computer, on cloud providers, and in your own data center. Read more and download on Machine’s blog post. Swarm is native clustering for Docker containers. It pools together several Docker Engines into a…

Continue reading...
Evan Hazlett

At DockerCon EU earlier this year, we announced Docker Machine, a tool that makes it really easy to go from “zero to Docker”. Machine creates Docker Engines on your computer, on cloud providers, and/or in your data center, and then configures the Docker client to securely talk to them. It works a bit like this: $ docker-machine create -d virtualbox dev [info] Downloading boot2docker… [info] Creating SSH key… [info] Creating VirtualBox VM… [info] Starting VirtualBox VM… [info] Waiting for VM to start… [info] “dev” has been created and is now the active machine. [info] To point your Docker client at…

Continue reading...