3 ms·
Unikernels are about security by auditability, mostly. Where containers have all of the security problems of two layers of operating systems and a container dae
by derefr 11y ago
Unikernels are about security by auditability, mostly. Where containers have all of the security problems of two layers of operating systems and a container daemon and a complete OS kernel (before you even get to a hypervisor), unikernels are just your app and the drivers it needs sitting on the hypervisor. Or even on bare metal.
It's a fairly different philosophy—I don't think anyone really cares about the performance aspect of it (those people care more about getting zero-copy low-level IO in userland while still reaping the "control-plane" benefits of having an OS, using e.g. Snabb Switch.)
It's more like the philosophy behind Erlang releases or black-box "appliance" VMs. Which is, basically, that you don't maintain "the OS" as a thing separate from your app; you just maintain "your app", and any bits of OS are basically part of the vendored deps of each successive app release.
- pjmlp 11y agoIf one looks at how many OSes evolved in the early days of computing history, there was always an overlap between rich language runtimes and the OS. The language runtime and libraries built on top of it were the OS. Seen by this lenses, POSIX could be seen as the C runtime, if one would stretch this example. So for me, it is quite natural that when one has languages with rich runtimes, the OS is just another layer that can be taken out and we can go back to the days when runtimes were mostly targeting bare-metal.