> Is that a good idea? Not if the service you’re running wants to be multi-process You can run multiple VMs. That's probably easier to use too, since you tooli

> Is that a good idea? Not if the service you’re running wants to be multi-process You can run multiple VMs. That's probably easier to use too, since you tooling for VMs is based around spinning up more machines, not processes. > not if you trust your kernel code more than the code of the service you run on top of it I don't really see how that applies. The application code is still the same. It's just that the OS doesn't exist any more. If it doesn't exist, it can't have bugs. > and not if you want the ability to look inside your containers (e.g. by ssh-ing into it) True. But I can't easily ssh inside a process either, which is what a unikernel is more comparable to. The only reason I ssh into my VMs is because the application process is wrapped up in an OS. If that OS did not exist, there would be less reason to peek into it.