Hacker Newsnew | past | comments | ask | show | jobs | submit | misterbisson's commentslogin

What if you could have isolation that's as good as or better than a VM in a container?


Then I'd be interested. But Solaris is x million lines of C code and the system call attack surface is huge, so I really don't think Joyent can offer that. Fundamentally if the author believes that you need a full traditional unix userland inside the container for debugging then they're never going to be able to offer that level of isolation.


Not inside the container. Containers are transparent to the host (Zones especially). You have tooling in the kernel, and you take coredumps when a container process dies.


See that's the model I'd expect to take - but that model makes perfect sense in the unikernel world too. So the author must be claiming that you need the debugging tools inside the container, otherwise the point about not having tcpdump etc. available makes no sense.


The problem with applying the same logic to hypervisor'd unikernels is that hypervisors make the guest system opaque. So how could you meaningfully run DTrace on that system?


How would that be possible? If you have a container with an attack surface as small as a VM, haven't you basically just created a VM by another name?


Yes, the the containers are running on bare-metal multi tenant hardware. Some of the savings comes from the performance gains as noted elsewhere, but additional savings comes from not having to pay for and manage an additional layer of virtual machines.

There's no need to provision anything other than the containers.


Actually, because the container runs on bare metal, there's no need to provision virtual machines before running containers.

Yes, the data center operator needs to install the hardware compute nodes, but after that there's no additional step to provision anything else but the containers themselves.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: