Skip to the content
Know your tech before you buy it. Makers: get listed from $49/mo

gVisor

gvisor.dev

  • Free plan
  • Linux
  • Self-hosted
7.4 Club score Visit gvisor.dev

What gVisor is

gVisor is an open-source Linux-compatible sandbox and application kernel for running containers while separating them from the host operating system. It is intended for untrusted workloads such as user-uploaded, LLM-generated, and third-party code. Its Sentry handles sandboxed applications’ system calls rather than sending them directly to the host; a Gofer process mediates filesystem access. The project describes a least-privilege design with a restrictive system call filter. It documents integrations with Docker, Kubernetes, containerd, and OCI runtimes, and can stream application trace points to an external threat-detection engine such as Falco. It can also checkpoint and restore containers. Most CUDA applications can run unmodified inside the sandbox with selected NVIDIA drivers, subject to GPU support limits. Installation requires Linux 5.6 or later on x86_64 or ARM64. gVisor is free and open source.

Who it suits

It suits Linux operators who need to run untrusted container workloads and want integrations with common container tools. Teams should account for its compatibility and performance trade-offs.

Good to know, and what to watch

  • Free and open-source software.
  • Integrates with Docker, Kubernetes, containerd, and OCI runtimes.
  • Can checkpoint and restore containers.
  • Streams trace points to external detection engines.
  • Supports many CUDA applications on selected NVIDIA drivers.
  • Requires Linux 5.6 or later.
  • Some system calls and /proc or /sys files are unsupported.
  • Higher per-system-call overhead and reduced compatibility are documented.
  • Generally does not protect against hardware side channels.

gVisor

Free

Free plan

The verdict

gVisor provides a container isolation layer for untrusted workloads, with integrations, trace streaming, and checkpointing. Its Linux requirements, compatibility gaps, and hardware side-channel limitations matter when assessing fit.

What the maker publishes

Architecture
A sandbox includes a Sentry application kernel that handles system calls and a Gofer process that mediates filesystem access. source
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. source
Compatibility caveat
The application compatibility list is best-effort and does not guarantee that applications marked compatible are fully functional. source
Compatibility limit
gVisor does not implement every system call, /proc file, or /sys file, so some application incompatibilities may occur. source
Container integrations
The project documents use with Docker, Kubernetes, containerd, and OCI runtimes. source
Container integrations
The OCI runtime runsc integrates with Docker, Kubernetes, and containerd. source
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. source
GPU limits
GPU support is limited to selected models, driver versions, capabilities, device files, ioctl calls, and platforms. source
GPU support
gVisor supports most CUDA applications on selected NVIDIA driver versions, and the GPU application can run unmodified inside the sandbox. source
Hardware security limit
gVisor generally does not protect against hardware side channels and relies on the host operating system and platform for those defenses. source
Kubernetes options
The documentation describes running gVisor with GKE Sandbox, Minikube, or Kubernetes nodes configured with containerd and the gVisor shim. source
License and availability
gVisor is described on its official site as open-source software. source
Performance trade-off
The documentation notes that gVisor has higher per-system-call overhead and reduced application compatibility compared with other isolation approaches. source
Product
gVisor is an open-source Linux-compatible sandbox for running containers. source
Purpose
gVisor is an open-source Linux-compatible sandbox and application kernel that isolates containers from the host operating system. source
Requirements
The installation guide says gVisor supports x86_64 and ARM64 and requires Linux 5.6 or later. source
Runtime monitoring
gVisor can stream application trace points to an external threat detection engine such as Falco to generate alerts. source
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. source
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. source
Support
The project directs users to GitHub issues, documentation, and mailing lists for support and community discussion. source
Supported host
Installation requires Linux 5.6 or later and supports x86_64 and ARM64. source
System call isolation
gVisor intercepts sandboxed applications’ system calls and implements them in its Sentry instead of passing them directly to the host. source
Untrusted workloads
It is intended to help safely run user-uploaded, LLM-generated, third-party, and other untrusted code. source
Use case
It is designed to isolate hosts from untrusted code, including user-uploaded, LLM-generated, and third-party code. source

Checked against the maker's pages on 4 Oct 2026.