diff options
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 134 |
1 files changed, 4 insertions, 130 deletions
@@ -1,131 +1,5 @@ - +# gVisor -[](https://buildkite.com/gvisor/pipeline) -[](https://github.com/google/gvisor/actions/workflows/issue_reviver.yml) -[](https://gitter.im/gvisor/community) -[](https://cs.opensource.google/gvisor/gvisor) - -## What is gVisor? - -**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)][oci] runtime called `runsc` that provides an -isolation boundary between the application and the host kernel. The `runsc` -runtime integrates with Docker and Kubernetes, making it simple to run sandboxed -containers. - -## Why does gVisor exist? - -Containers are not a [**sandbox**][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. - -## Documentation - -User documentation and technical architecture, including quick start guides, can -be found at [gvisor.dev][gvisor-dev]. - -## 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][bazel] and other build -dependencies are wrapped in a build container. It is possible to use -[bazel][bazel] directly, or type `make help` for standard targets. - -### Requirements - -Make sure the following dependencies are installed: - -* Linux 4.14.77+ ([older linux][old-linux]) -* [Docker version 17.09.0 or greater][docker] - -### Building - -Build and install the `runsc` binary: - -```sh -mkdir -p bin -make copy TARGETS=runsc DESTINATION=bin/ -sudo cp ./bin/runsc /usr/local/bin -``` - -### Testing - -To run standard test suites, you can use: - -```sh -make unit-tests -make tests -``` - -To run specific tests, you can specify the target: - -```sh -make test TARGETS="//runsc:version_test" -``` - -### Using `go get` - -This project uses [bazel][bazel] to build and manage dependencies. A synthetic -`go` branch is maintained that is compatible with standard `go` tooling for -convenience. - -For example, to build and install `runsc` directly from this branch: - -```sh -echo "module runsc" > go.mod -GO111MODULE=on go get gvisor.dev/gvisor/runsc@go -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 binary for `containerd`: - -```sh -GO111MODULE=on sudo -E go build -o /usr/local/bin/containerd-shim-runsc-v1 gvisor.dev/gvisor/shim -``` - -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 -`master` branch, which is then reflected into the `go` branch. - -## Community & Governance - -See [GOVERNANCE.md](GOVERNANCE.md) for project governance information. - -The [gvisor-users mailing list][gvisor-users-list] and -[gvisor-dev mailing list][gvisor-dev-list] are good starting points for -questions and discussion. - -## Security Policy - -See [SECURITY.md](SECURITY.md). - -## Contributing - -See [Contributing.md](CONTRIBUTING.md). - -[bazel]: https://bazel.build -[docker]: https://www.docker.com -[gvisor-users-list]: https://groups.google.com/forum/#!forum/gvisor-users -[gvisor-dev]: https://gvisor.dev -[gvisor-dev-list]: https://groups.google.com/forum/#!forum/gvisor-dev -[oci]: https://www.opencontainers.org -[old-linux]: https://gvisor.dev/docs/user_guide/networking/#gso -[sandbox]: https://en.wikipedia.org/wiki/Sandbox_(computer_security) +This branch is a synthetic branch, containing only Go sources, that is +compatible with standard Go tools. See the master branch for authoritative +sources and tests. |