We’re excited to include the following guest blog post by our friends at Domino. Domino is a PaaS for data science — our goal is to give analysts and researchers easy access to powerful infrastructure, so they can focus on their analysis instead of worrying about custom tooling and environment setup. Docker has been enormously helpful to us, saving us many man-months of engineering effort. Before describing that in more detail, we’ll provide some context about what we mean by providing “powerful infrastructure.” Essentially, Domino provides three things:
The community has been critical to Docker since its inception. While we’ve always known how awesome the community is, we decided to pull some stats from the Docker Repository on Github to help quantify the awesomeness. The table below shows the total contributions for Docker in terms of code additions, deletions and commits. *Docker Project Stats on 10/29/2013: To avoid stressing GitHub’s APIs, we crunched the data locally.
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….
This morning, we officially announced that dotCloud, Inc. is changing its name to Docker, Inc. This change is more than just a new name or new website. Since releasing Docker in March, we have seen it become not just a rapidly growing open source project, but also the center of a vibrant ecosystem that is driving a significant change in how software is written, built, and deployed. While Docker, Inc. will continue to offer PaaS services under the dotCloud brand, we will be devoting the vast majority of our resources towards growing Docker and the Docker ecosystem, and have fundamentally re-oriented…
Last month we asked the Docker community to vote for the name of the Docker whale. We received 411 votes and today we are excited to announce that the community chose Moby Dock.
Linux Containers rely on control groups which not only track groups of processes, but also expose a lot of metrics about CPU, memory, and block I/O usage. We will see how to access those metrics, and how to obtain network usage metrics as well. This is relevant for “pure” LXC containers, as well as for Docker containers.
October 1st was not only the date of our Docker Hack Day #7 but also the first Online 101 Session broadcasted through google hangout on air. Below you will find a few comments, photos and videos of these two events. Online 101 Session: Nick Stinemates (picture here below) gave an introduction to what Docker is all about and how you can use Docker for Multi-Cloud Deployment. Over the next few months, we will be having more online sessions to make Docker accessible to our growing community overseas.
One of the (many!) features of Docker 0.6 is the new “privileged” mode for containers. It allows you to run some containers with (almost) all the capabilities of their host machine, regarding kernel features and device access. Among the (many!) possibilities of the “privileged” mode, you can now run Docker within Docker itself. First, we will see how to make that happen; next, we will explain what is involved under the hood, and finally, we will show something even more powerful than Docker in Docker! See Docker-in-Docker in action If you have Docker 0.6, all you have to do is:…