3 ms·
The vast majority of people who seem to want containers, are those who have embraced the idea that developers can manage servers because they can write (or copy
by stephenr 11y ago
The vast majority of people who seem to want containers, are those who have embraced the idea that developers can manage servers because they can write (or copy) a Dockerfile and push a container to a container service on AWS or Google Cloud.
In those situations you specifically do want containers on VMs because Docker containers do not provide the same level of security and isolation that VMs do.
- scprodigy 11y agoPhoton is built for this case: a minimalist OS to run only as guest. However, check out hyper.sh, the project uses hypervisors to run Docker images, which completely eliminates the need of guest OS, making the whole stack immutable while just offering the hypervisor-level isolation. In my opinion, Hyper is the way to go, instead of the minimalist guest OS distro.
- deleted 11y ago[deleted]
- deleted 11y ago[deleted]
- stock_toaster 11y agoI recall watching a talk (given by @bcantrill I think it was?) where SmartOS had implemented the docker api, but ran the actual "container" via linux emulation, inside a zone. I think they named it "lx branded zones" or something similar. I could see vmware doing something like that -- implementing the docker api, but actually running containers on very lightweight vms, so they can leverage their existing virt infrastructure (memory ballooning, cpu allocation, migration, etc) with it.
- stephenr 11y agoSo you have a docker container inside Linux emulation inside a Solaris-style zone on a SmartOS host. This is the opposite of "turtles all the way down" - it's like a veritable layer cake of system isolation. It's the turducken of server systems.
- stock_toaster 11y agoNot quite. Docker is just the api. So you just have linux emulation (which is apparently some light weight api call mapping) inside a zone. So maybe ducken without the turd? ;)