stphantom
Re:Open-sourcing gVisor, a sandboxed container runtime
on Wednesday May 02, 2018 @11:27AM (#16977832)
You are right in that ptrace is slow and nasty. The key problem, I believe, is the tracer-tracee mode that involves two host processes and the switch is asynchronous (ptrace(SYSEMU) and then waitpid).
We do have the KVM platform that offers the synchronous switch, which performs better if you have bare-metal virtualization support.
Re:Open-sourcing gVisor, a sandboxed container runtime
on Wednesday May 02, 2018 @09:38AM (#16976710)
Do you mean "rump kernels" or "Rumprun kernel"?
The former is a set of kernel libraries derived from NetBSD, and the latter is a Unikernel built based on the former. gVisor is different in a couple of ways: 1) gVisor is written from scratch using Go for its memory and type safety; 2) gVisor tends to be compatible with Linux which most people use. In theory, gVisor can be restructured as a Unikernel, but we still like to pertain the ring privilege boundary for additional isolation. We are working on an academic paper which will have more details.
I work on gVisor (TL/M and Co-Founder).