Github url


by google

google /gvisor

Application Kernel for Containers

10.2K Stars 754 Forks Last release: Not found Apache License 2.0 3.9K Commits 23 Releases

Available items

No Items, yet!

The developer of this repository has not created any items for sale yet. Need a bug fixed? Help with integration? A different license? Create a request here:


gVisor chat

What is gVisor?

gVisor is an application kernel, written in Go, that implements a substantial portion of the Linux system surface. It includes anOpen Container Initiative (OCI) runtime called


that provides an isolation boundary between the application and the host kernel. The


runtime integrates with Docker and Kubernetes, making it simple to run sandboxed containers.

Why does gVisor exist?

Containers are not a sandbox. While containers have revolutionized how we develop, package, and deploy applications, using them to run untrusted or potentially malicious code without additional isolation is not a good idea. While using a single, shared kernel allows for efficiency and performance gains, it also means that container escape is possible with a single vulnerability.

gVisor is an application kernel for containers. It limits the host kernel surface accessible to the application while still giving the application access to all the features it expects. Unlike most kernels, gVisor does not assume or require a fixed set of physical resources; instead, it leverages existing host kernel functionality and runs as a normal process. In other words, gVisor implements Linux by way of Linux.

gVisor should not be confused with technologies and tools to harden containers against external threats, provide additional integrity checks, or limit the scope of access for a service. One should always be careful about what data is made available to a container.


User documentation and technical architecture, including quick start guides, can be found at

Installing from source

gVisor builds on x86_64 and ARM64. Other architectures may become available in the future.

For the purposes of these instructions, bazel and other build dependencies are wrapped in a build container. It is possible to usebazel directly, or type

make help

for standard targets.


Make sure the following dependencies are installed:


Build and install the



make runsc sudo cp ./bazel-bin/runsc/linux\_amd64\_pure\_stripped/runsc /usr/local/bin


To run standard test suites, you can use:

make unit-tests make tests

To run specific tests, you can specify the target:

make test TARGETS="//runsc:version\_test"


go get

This project uses bazel to build and manage dependencies. A synthetic


branch is maintained that is compatible with standard


tooling for convenience.

For example, to build and install


directly from this branch:

echo "module runsc" \> go.mod GO111MODULE=on go get[email protected] CGO\_ENABLED=0 GO111MODULE=on sudo -E go build -o /usr/local/bin/runsc

Subsequently, you can build and install the shim binaries for



GO111MODULE=on sudo -E go build -o /usr/local/bin/gvisor-containerd-shim GO111MODULE=on sudo -E go build -o /usr/local/bin/containerd-shim-runsc-v1

Note that this branch is supported in a best effort capacity, and direct development on this branch is not supported. Development should occur on the


branch, which is then reflected into the



Community & Governance

See for project governance information.

The gvisor-users mailing list andgvisor-dev mailing list are good starting points for questions and discussion.

Security Policy




We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.