Freedom251 › Container Engines
gVisor
What gVisor is
gVisor is a free, open-source Linux-compatible sandbox for running containers and keeping untrusted code separate from the host operating system. It is designed for workloads such as user-uploaded, LLM-generated, or third-party code. Its Sentry handles sandboxed applications’ system calls rather than sending them directly to the host, while a Gofer process mediates filesystem access. The Sentry’s host system call access is minimized, and gVisor uses least privileges and a restrictive system call filter. The project documents integrations with Docker, Kubernetes, containerd, and OCI runtimes, as well as Kubernetes deployment options including GKE Sandbox and Minikube. It can stream application trace points to an external detection engine such as Falco and checkpoint and restore containers. Most CUDA applications can run unmodified in the sandbox with selected NVIDIA drivers, subject to limits. Installation requires Linux 5.6 or later on x86_64 or ARM64. Some applications may not work fully, and gVisor generally does not protect against hardware side channels.
Who it suits
gVisor suits teams running containerized, untrusted workloads on Linux, including user-submitted or generated code. It may also suit Kubernetes operators who need its documented integrations or checkpointing and restore.
What it does well
- Free and open-source software.
- Integrates with Docker, Kubernetes, containerd, and OCI runtimes.
- Can checkpoint and restore containers.
- Supports most CUDA applications with selected NVIDIA drivers.
What to know first
- Requires Linux 5.6 or later.
- Some system calls and /proc or /sys files are unsupported.
- Compatibility listings do not guarantee full functionality.
- Generally does not protect against hardware side channels.
Limits
The free plan is open-source software and requires Linux 5.6 or later on x86_64 or ARM64. gVisor does not implement every system call, /proc file, or /sys file, and its compatibility list is best-effort; GPU support is restricted to selected models, drivers, capabilities, device files, ioctl calls, and platforms.
Plans
| Plan | Billed and limits | Price |
|---|---|---|
| gVisor | Open-source Linux-compatible sandbox; requires Linux 5.6+ and x86_64 or ARM64 | Free |
As gvisor.dev lists them, read 4 Oct 2026. The maker's own page has the final word.
Getting started
- Open the gVisor website and review the installation documentation.
- Use a Linux host running version 5.6 or later on x86_64 or ARM64.
- Choose a documented route such as Docker, Kubernetes, containerd, or an OCI runtime.
- Configure gVisor for the container environment; Kubernetes options include GKE Sandbox, Minikube, or a node using containerd and the gVisor shim.
Verdict
gVisor provides a Linux container sandbox with syscall handling, filesystem mediation, and integrations for common container environments. Check application compatibility and the Linux and hardware requirements before adopting it.
Questions
Is gVisor free?
Yes. The listed gVisor plan is free, and the project describes the software as open source.
Which platforms does gVisor support?
It supports Linux hosts, including self-hosted installations. The installation requirements specify Linux 5.6 or later and x86_64 or ARM64.
Does gVisor work with Kubernetes and Docker?
The project documents use with Docker, Kubernetes, containerd, and OCI runtimes. Kubernetes options include GKE Sandbox, Minikube, and nodes configured with containerd and the gVisor shim.
Does gVisor support GPUs?
It supports most CUDA applications on selected NVIDIA driver versions, and applications can run unmodified inside the sandbox. Support is limited by models, drivers, capabilities, device files, ioctl calls, and platforms.
What are gVisor's compatibility limits?
It does not implement every system call, /proc file, or /sys file, so some applications may be incompatible. Its compatibility list is best-effort and does not guarantee full functionality.
How can users get support?
The project directs users to its GitHub issues, documentation, and mailing lists for support and community discussion.
Facts from gVisor's own pages
- Architecture
- A sandbox includes a Sentry application kernel that handles system calls and a Gofer process that mediates filesystem access. · gvisor.dev, 4 Oct 2026
- Checkpoint and restore
- gVisor can checkpoint and restore containers for uses such as caching warmed services, resuming workloads on other machines, and saving state for forensics. · gvisor.dev, 4 Oct 2026
- Compatibility caveat
- The application compatibility list is best-effort and does not guarantee that applications marked compatible are fully functional. · gvisor.dev, 4 Oct 2026
- Compatibility limit
- gVisor does not implement every system call, /proc file, or /sys file, so some application incompatibilities may occur. · gvisor.dev, 4 Oct 2026
- Container integrations
- The OCI runtime runsc integrates with Docker, Kubernetes, and containerd. · gvisor.dev, 4 Oct 2026
- Defense in depth
- The Sentry’s access to host system calls is minimized, and the site says gVisor runs with least privileges and a strict system call filter. · gvisor.dev, 4 Oct 2026
- GPU limits
- GPU support is limited to selected models, driver versions, capabilities, device files, ioctl calls, and platforms. · gvisor.dev, 4 Oct 2026
- GPU support
- gVisor supports most CUDA applications on selected NVIDIA driver versions, and the GPU application can run unmodified inside the sandbox. · gvisor.dev, 4 Oct 2026
- Hardware security limit
- gVisor generally does not protect against hardware side channels and relies on the host operating system and platform for those defenses. · gvisor.dev, 4 Oct 2026
- Kubernetes options
- The documentation describes running gVisor with GKE Sandbox, Minikube, or Kubernetes nodes configured with containerd and the gVisor shim. · gvisor.dev, 4 Oct 2026
- License and availability
- gVisor is described on its official site as open-source software. · gvisor.dev, 4 Oct 2026
- Performance trade-off
- The documentation notes that gVisor has higher per-system-call overhead and reduced application compatibility compared with other isolation approaches. · gvisor.dev, 4 Oct 2026
- Product
- gVisor is an open-source Linux-compatible sandbox for running containers. · gvisor.dev, 4 Oct 2026
- Purpose
- gVisor is an open-source Linux-compatible sandbox and application kernel that isolates containers from the host operating system. · gvisor.dev, 4 Oct 2026
- Requirements
- The installation guide says gVisor supports x86_64 and ARM64 and requires Linux 5.6 or later. · gvisor.dev, 4 Oct 2026
- Runtime monitoring
- gVisor can stream application trace points to an external threat detection engine such as Falco to generate alerts. · gvisor.dev, 4 Oct 2026
- Security design
- The Linux kernel and network stack components are written in Go, and gVisor runs with least privileges and a restrictive system call filter. · gvisor.dev, 4 Oct 2026
- Security reporting
- The project asks that sensitive security reports be sent to its security mailing list or submitted privately through GitHub advisories, and says a response is typically provided within 48 hours. · gvisor.dev, 4 Oct 2026
- Support
- The project directs users to GitHub issues, documentation, and mailing lists for support and community discussion. · gvisor.dev, 4 Oct 2026
- Supported host
- Installation requires Linux 5.6 or later and supports x86_64 and ARM64. · gvisor.dev, 4 Oct 2026
- System call isolation
- gVisor intercepts sandboxed applications’ system calls and implements them in its Sentry instead of passing them directly to the host. · gvisor.dev, 4 Oct 2026
- Untrusted workloads
- It is intended to help safely run user-uploaded, LLM-generated, third-party, and other untrusted code. · gvisor.dev, 4 Oct 2026
- Use case
- It is designed to isolate hosts from untrusted code, including user-uploaded, LLM-generated, and third-party code. · gvisor.dev, 4 Oct 2026
Where gVisor stands on Freedom251
- Container Engines#11 of 31
- Container Runtime Software#13 of 28