News for hackers. Stuff that matters.
Re:Sandboxing and workload isolation by mrkurt on Thursday July 30, 2020 @02:59PM (#24001708)
We've been playing a lot with OSv. But unikernels aren't strictly sandboxing or isolation.

If you're deploying a unikernel to ec2, you're just using their underlying isolation. You can't safely deploy multiple unikernels on the same ec2 instances without figuring out your own, nested isolation.

Re:Sandboxing and workload isolation by eyberg on Thursday July 30, 2020 @03:06PM (#24001770)
Sure - the hypervisor is the isolation vehicle - the same as firecracker.

The only? reason I can see for wanting to deploy N unikernels to one AWS instance is if you want full control on the orchestration of things like multi-tenancy, however, it is very much possible and it is possible on GCloud as well. It should be noted that you are in the same boat as firecracker here. They both use virtualization.

Re:Sandboxing and workload isolation by yencabulator on Friday July 31, 2020 @05:21PM (#24014296)
The usual reason to want to do N things with 1 piece of hardware is cost savings.