Michael Crosby

Progress Report: Open Container Initiative

Last June, we launched the Open Container Initiative, under the auspices of the Linux Foundation. The OCI was designed to collaborate on an open, standard container format and runtime in order to preserve that portability and interoperability for users. We’re very happy with the progress OCI has made, and we wanted to share that with you.

Michael Crosby

Dolly Demo at LinuxCon: Rapid cloning of existing services with runC

At LinuxCon in August, I presented a keynote demo with Diogo Mónica and Marianna Tessel. The goal of the demo was to show that checkpoint and restore of containers can not only be used for the migration of stateful services i.e. stopping the service and moving it, but also for rapid cloning of existing services. Cloning existing services quickly is one way to get an application to scale as demand increases. The most important problem we had to tackle was cache warming. A cache takes a long time to warm and can hinder the ability to scale out an application horizontally. By cloning an existing cache we do not have to pay the cost to fill it, allowing us to quickly clone our services across multiple containers. You can check out the code on github.

Michael Crosby

Open Container Format Progress Report

Follow Up from Open Container Initiative (formerly Project) Announcement of 6/22 written by Michael Crosby, Chief Maintainer of Docker, Inc. Approximately one month ago, we announced the creation of the Open Container Initiative*, under the auspices of the Linux Foundation for the express purpose of defining common specifications around container format and runtime.  Docker donated both our base container format and runtime, runC, and we began working with maintainers of AppC to create a common set of specifications. I’m happy to share that there has been a lot of progress in the past month. After the first few weeks of work for the OCF specification and runC most of the unanswered questions have either been solved or progress is being made on the GitHub repositories.  We are sprinting to get the first draft out to the community by the end Continue reading…

Michael Crosby

Docker 1.5: IPv6 support, read-only containers, stats, “named Dockerfiles” and more

The Docker project team wanted to start the new year out right with something awesome; that’s why we’re super excited to announce the first Docker release for 2015. We’ve smashed many long-standing, annoying bugs and merged a few awesome features that both the community and maintainers are excited about. Let’s check out what’s in Docker 1.5.

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.

Michael Crosby

Docker 0.6.5: name your containers, link them together, selectively publish ports, and more

Today we’re happy to announce Docker 0.6.5. Don’t be fooled by the version number: this is a significant release! Think of it as a preparation for 0.7, which will be even more significant. In addition to numerous bug fixes, this release introduces container naming, links between containers, better host integration, and advanced port redirects. A big thank you to (in no particular order) to Paul Nasrat, Tianon Gravi, Edmund Wagner, Travis Cline, Gurjeet Singh, Justin Force, Johan Euphrosine, Ole Reifschneider, Will Rouesnel, Alex Larsson, Greg Thornton, Sven Dowideit, Scott Bessler, Todd Lunter, Vladimir Rutsky, Nicolas Dudebout, Nicolas Dudebout, Roger Peppe, Jerome Petazzoni for your contributions. Not bad for a minor release! (sorry if we forgot anyone).  

Michael Crosby

Introducing the Dockerfile tutorial

Dockerfiles can be viewed as an image representation. They provide a simple syntax for building images and they are a great way to automate and script the images creation. If you are really serious about Docker, you should master the Dockerfile syntax. To help you learn the Dockerfile syntax, we did put together a very easy to follow tutorial. In the next couple of months we will release several levels, one  at a time, so you could master the Dockerfile syntax quickly, instruction by instruction. At the end of each level you will find tests to check your knowledge. Ready? Start  Level 0