6 ms·
It runs directly under KVM/Xen/Virtualbox/etc. Essentially it is a Linux Kernel, root filesystem and minimal set of services to be able to launch and manage con
by philips 13y ago
It runs directly under KVM/Xen/Virtualbox/etc. Essentially it is a Linux Kernel, root filesystem and minimal set of services to be able to launch and manage containers.
- wmf 13y agoI'm not sure why there's so much emphasis on "yo dawg" double virtualization. I'd be more interested in PXE booting this thing on bare metal.
- lotyrin 13y agoContainers aren't virtualized, they're just isolated from each other. That's why they're cool. Instead of working at the IaaS level for each app, you can have IaaS provide a cluster for containers to run in, and then put up a personal PaaS built out of containers - have more flexibility, spend less money, app folks don't have to worry about infra as much. And in the case that you're at a scale that you can use real hardware (or a hybrid approach), it's easy to move without the containers having to worry about it.
- philips 13y agoThat is something we would like to do. We started with virtualized hardware because it is easy for people to try out on their own stuff or other providers. Also, we are just getting started and didn't want to try and support everything day 0. :)
- GhotiFish 13y agoI get the sense this is sort of the opposite of that. It's not visualization. It's programs, isolated from eachother, running on an operating system.