4 ms·
Well they are both, it is a weaker VM as far as capabilities, but also have more ability than a single isolated OS process. There is no need to blackbox the co
by rdtsc 13y ago
Well they are both, it is a weaker VM as far as capabilities, but also have more ability than a single isolated OS process.
There is no need to blackbox the concept un-necessarily. It is an LXC container, read about LXC containers, its capabilities and restrictions. If you are building at core of your infrastructure don't trust simplistic mental analogies from HN.
Then Docker works on top of that. Read about what Docker adds or restricts on top of the base LXC containers.
I also think Docker is a little too wishy washy in their marketing and there are enough people who get confused about what exactly is going on underneath.
From the slides "More technical explanations: Run everywhere, regardless of kernel version [+], regardless of host distro, physical or virtual, cloud or not [o]
[+] kernel version must be 2.6.32+
[o] container and host architecture must match.
"
No mention of LXC containers, and that is a "technical" description. Why not just put a mention of the underlying core technology? It might change tomorrow sure and just update.
- pekk 13y agoThey do mention LXC on their site. It isn't necessary to harp on it everywhere. I don't see that people are confused about what is going on. I thought it was clear that Docker intended to abstract some of the platform-specific details like using LXC, and focus on making a standard interface for encapsulating and managing services. I find it misleading to talk like Docker is just LXC, or a shell script for running LXC, with no contribution of its own.
- rdtsc 13y ago> I don't see that people are confused about what is going on. I can see it in these discussions and in personal conversations. Yeah one can say "their fault didn't read docs". > They do mention LXC on their site. Where? Click on "Learn More". Switch through slides, get to "Technical Details", nothing there. Click on "The whole story". In a 10-20 page "super-detailed" technical explanation it is mentioned twice in passing. > I thought it was clear that Docker intended to abstract some of the platform-specific details like using LXC Clear to you and me, not clear to quite a few people. > and focus on making a standard interface for encapsulating and managing services. And that is my beef with it, selling complete black boxes and then have people wonder if there are unicorns inside, is it a VM, is it a container... If they just mentioned exactly that their technology is based on it would make it easier. Are they afraid they'll get sued by LXC creators? I don't understand why go to great lengths beating around the bush about it. > I find it misleading to talk like Docker is just LXC I think it is even more misleading to not talk about the core underlying technology and then say what they add on top of it.
- derefr 13y ago> And that is my beef with it, selling complete black boxes and then have people wonder if there are unicorns inside, is it a VM, is it a container... If they just mentioned exactly that their technology is based on it would make it easier. Docker isn't "selling" a technology, though, they're selling a container standard. Right now, the containers people are making are all Linux-ELF-x64 ABI containers, so they're run using LXC. Future containers, though, could run on Solaris zones, or BSD jails, or OSX sandboxes, or full VMs instead. And they'd still be "Docker containers." That's the thing Docker is trying to get people interested in--pluggable units of backend-irrelevant computation. LXC is just how that's implemented for the Linux-ABI containers, which are their MVP.