5 ms·
1. Google Container Engine runs Docker containers, the same as other providers like AWS EC2 Container Service and Joyent Compute Service. 2. I don't understand
by sciurus 12y ago
1. Google Container Engine runs Docker containers, the same as other providers like AWS EC2 Container Service and Joyent Compute Service.
2. I don't understand what you mean.
3. You run your containers on virtual machines dedicated to you, so you rely on the hypervisor for security.
4. Cgroups is one of the technologies that linux containers are built on. What is your point?
5. Google is building their container service on docker and kubernetes [0]. Both of these are open source, already adapted by multiple providers, and possible for you to run yourself.
[0] http://googlecloudplatform.blogspot.com/2015/01/everything-you-wanted-to-know-about-Kubernetes-but-were-afraid-to-ask.html http://googlecloudplatform.blogspot.com/2015/01/everything-y...
- contingencies 12y ago1. Yeah. Which is a tangent to the point that they spent a paragraph talking up the nominal benefits of distributing an entire container without facing either the reality that there is no standardized format (yes, really, look it up) or the necessary loss of binary portability. So yeah, marketing drivel .. all benefits, no frank discussion of drawbacks. 2. From the article, it seems like they are encouraging people to build their own cluster atop their platform rather than using a packaged cluster service. 3. OK. So allegedly two layers here. That's a lot better than one, though it makes you wonder how they schedule client slash client cgroup association across physical hardware (ie. VMs). 4. That's just a paragraph of fluff around cgroups, was my point. 5. The fact is you can't migrate easily between arbitrary providers because nothing offers you that level of abstraction.