The Enemy Within: Running Untrusted Code with gVisor
summary
gVisor virtualizes at the OS level with a user-space kernel (Sentry) plus a separate gopher process, intercepting syscalls via ptrace or KVM so the host only ever sees a greatly reduced set — about 30 syscalls allowed — and the sandbox runs as UID nobody. It integrates with containerd / Kubernetes as a runtime class, supports multiple containers per pod, and ships a working minikube add-on and GKE sandbox for real deployments.
AI-written summary · about
chapters (8)
- 0:00Introduction to gVisor
- 1:00The need for sandboxing
- 5:21Sandboxing alternatives
- 11:40The gVisor architecture
- 17:00Integration and runtime
- 22:59Design principles
- 29:01Security considerations
- 31:49Getting started and wrap-up
related talks
35mThe Enemy Within: Running Untrusted Code with gVisor
25mIsolating Kubernetes Workloads with gVisor
40mContainer Isolation at Scale (Introducing gVisor) - Dawn Chen & Zhengyu He, Google
30mAccelerating AI Securely with GVisor
27mgVisor Container on Arm64: Let‘s Talk about Our Progress!
37mA New Secure Container Solution on Arm Platform: gVisor
06mKeynote: Cloud Native Observability & Security from Google Cloud
19mSandbox to confidential containers: A brief on the evolution of container isolation