google/gvisor

Application Kernel for Containers

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 1 minute ago
Added to GitGenius on September 3rd, 2026
Created on April 26th, 2018
Open Issues & Pull Requests: 868 (+0)
GitHub issues: Enabled
Number of forks: 1,975
Total Stargazers: 19,240 (+0)
Total Subscribers: 330 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 6.4 hours
Mean response time: 40.5 days
90th percentile: 31.1 days
Tracked items: 457

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 81% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "area: compatibility" is answered fastest, typically in under an hour, while "area: filesystem" waits about 7 days. 13% of tracked open issues have had no activity in three months. Only 4% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 222
New in 7 days: 20
Closed in 7 days: 9
Avg open age: 576 days
Stale 30+ days: 127
Stale 90+ days: 72

Recent activity

Opened in 7 days: 13
Closed in 7 days: 8
Comments in 7 days: 2
Events in 7 days: 12

Top labels

  • type: bug (264)
  • type: enhancement (177)
  • stale-issue (50)
  • status: help wanted (34)
  • area: networking (29)
  • good first issue (22)
  • area: gpu (21)
  • area: compatibility (20)

Detailed Description

gVisor is an application kernel for containers that provides strong isolation between running applications and the host operating system by implementing a Linux-like interface in userspace using Go.

gVisor addresses the security risk that containers share a kernel with the host, making container escape possible through a single vulnerability. Rather than filtering syscalls or wrapping Linux isolation primitives, it takes a distinct approach by implementing a full Linux kernel in userspace as a memory-safe application. This allows it to limit the host kernel surface accessible to applications while maintaining the lower resource footprint and fast startup of regular processes. The project includes runsc, an OCI-compliant runtime that integrates with Docker and Kubernetes to make sandboxed containers work with existing container tooling.

Adoption suits teams running untrusted or potentially malicious code who need stronger isolation than standard containers provide but want to avoid the overhead of full virtual machines. The tool works on x86_64 and ARM64 architectures and requires Linux 5.6 or later. It is explicitly not a syscall filter, a wrapper over Linux isolation primitives, or a traditional VM, but rather occupies a distinct middle ground offering security benefits of VMs with the efficiency of containerized applications.

The project receives almost all of its open issues from outside users rather than the core team, indicating a substantial base of adopters reporting real-world use. Maintainers typically respond to new issues and pull requests within a day. Work in the issue tracker is dominated by bug reports, enhancement requests, and stale issue management.