Application Kernel for Containers
gVisor is an application kernel, written in Go, that implements a substantial portion of the Linux system surface. It includes an Open Container Initiative (OCI) runtime called
runscthat provides an isolation boundary between the application and the host kernel. The
runscruntime integrates with Docker and Kubernetes, making it simple to run sandboxed containers.
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 gvisor.dev.
gVisor builds on x86_64 and ARM64. Other architectures may become available in the future.
make helpfor 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"
This project uses bazel to build and manage dependencies. A synthetic
gobranch is maintained that is compatible with standard
gotooling for convenience.
For example, to build and install
runscdirectly from this branch:
echo "module runsc" > go.mod GO111MODULE=on go get gvisor.dev/gvisor/[email protected] CGO_ENABLED=0 GO111MODULE=on sudo -E go build -o /usr/local/bin/runsc gvisor.dev/gvisor/runsc
Subsequently, you can build and install the shim binaries for
GO111MODULE=on sudo -E go build -o /usr/local/bin/gvisor-containerd-shim gvisor.dev/gvisor/shim/v1 GO111MODULE=on sudo -E go build -o /usr/local/bin/containerd-shim-runsc-v1 gvisor.dev/gvisor/shim/v2
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
masterbranch, which is then reflected into the
See GOVERNANCE.md for project governance information.