My slides from the talk at GlueCon: <a href="https://speakerdeck.com/jbeda/containers-at-scale" rel="nofollow">https://speakerdeck.com/jbeda/containers-at-scale</a>
Google deserves a shout-out for embracing Docker in a really constructive way. In addition to building cool tools on top of it (like the one linked here), they are also contributing real engineering effort into the upstream Docker project itself. For example Victor and Rohit from the Google LMCTFY team are now active maintainers of libcontainer (<a href="https://github.com/dotcloud/docker/blob/master/pkg/libcontainer/MAINTAINERS" rel="nofollow">https://github.com/dotcloud/docker/blob/master/pkg/libcontai...</a>)
I'm looking forward to digging through the agent, but I'm a bit surprised that it's in Python rather than Go, given the minimal nature of the "host" OS.<p>If any Google folks or other knowledgable people are around, I'd be curious to know what went in to that choice.
Fascinating, however I'm quite curious about whether they took a serious look at utilizing CoreOS over Debian 7 (and if so, why Debian 7 was chosen instead).
Is this a way to run docker/container in a GCE/VM, or does the docker/container run on top of the base OS, so that your application can run at bare metal speed, without the overhead of of a VM.
Now major players start to adopt Docker, I wonder whether they should standardized manifest format?<p>GCE use diff format than AWS BE, it would be good to have standard so more love for DevOps. :)