4 ms·
How is this different from Intel Clear Containers?
by rwmj 9y ago
How is this different from Intel Clear Containers?
- bestouff 9y agoHow far is it from CloudABI ?
- floatboth 9y agoHa, actually it reminded me of CloudABI's userspace translator. But it's the kernel implementation that's actually secure.
- szemet 9y agoClear Containers are a full HW virtualization with a full linux kernel - just tuned to start very fast. (The OP even have figures to explain the differences e.g. at "Existing VM-based container technology")
- cpuguy83 9y agoThis implements system calls in user space, intercepting those calls via ptrace (though there is a KVM backend as well). Honestly I don't see an advantage to this over a stricter seccomp policy, and most definitely slower.
- cpuguy83 9y agoI retract the statement that I don't see the advantage. See https://twitter.com/rauchg/status/991850924057350144 https://twitter.com/rauchg/status/991850924057350144 for why. Basically run `mount` in a gvisor container and run `mount` in a runc container and see the major differences there. Just one example, but as you can see, linux mount namespaces tend to leak lots of mount information. some of it could be cleaned up with additional unmounts after setting up the new root for the container, but knowing what to unmount is not so simple (plus it's just janky AF).
- jsolson 9y agoClear Containers has merged into Kata Containers -- gVisor offers a different set of tradeoffs than Kata (or CC). The big one is resource footprint -- gVisor will typically be lower, often much lower than Kata. On the other hand, for very syscall heavy workloads Kata needn't take exits (while gVisor exits for many syscalls that make it beyond the sandbox), so performance on gVisor will have higher variance with respect to syscall rate. Kata also offers the opportunity for sandboxing things like kernel driver blobs (since you get a whole new Linux ring 0) while gVisor relies on the host kernel for many tasks. There's a lot of overlap between cgroups, gVisor-style sandboxes, and VM-style sandboxes like Kata. The tradeoffs between them are mostly with respect to compatibility, robustness of the security boundaries, and performance. So, you know, the usual suspects. We've reached a stage where we probably need better vocabulary for describing these tradeoffs :) (I work on "near" the gVisor folks at Google, and I'm involved in the Kata community)