gvisor - Container Runtime Sandbox

Age	Commit message (Collapse)	Author
2020-05-12	Merge pull request #2513 from amscanne:website-integrated	gVisor bot
	PiperOrigin-RevId: 311184385
2020-05-06	Adapt website to use g3doc sources and bazel.	Adin Scannell
	This adapts the merged website repository to use the image and bazel build framework. It explicitly avoids the container_image rules provided by bazel, opting instead to build with direct docker commands when necessary. The relevant build commands are incorporated into the top-level Makefile.
2020-04-24	Standardize all Docker images.	Adin Scannell
	This change moves all Docker images to a standard location, and abstracts the build process so that they can be maintained in an automated fashion. This also allows the images to be architecture-independent. All images will now be referred to by the test framework via the canonical `gvisor.dev/images/<name>`, where `<name>` is a function of the path within the source tree. In a subsequent change, continuous integration will be added so that the images will always be correct and available locally. In the end, using `bazel` for Docker containers is simply not possible. Given that we already have the need to use `make` with the base container (for Docker), we extend this approach to get more flexibility. This change also adds a self-documenting and powerful Makefile that is intended to replace the collection of scripts in scripts. Canonical (self-documenting) targets can be added here for targets that understand which images need to be loaded and/or built. PiperOrigin-RevId: 308322438
2020-02-21	arm64: add a travis build ci	Andrei Vagin
	Build runsc and run "runsc do ls". Signed-off-by: Andrei Vagin <avagin@gmail.com>
2019-12-02	Allow non-unique UIDs in bazel docker containers	Ian Lewis
	Allow non-unique UIDs in the bazel docker container in order to avoid failures using host UIDs that are already present in the image. Issue #1267 PiperOrigin-RevId: 283456369
2019-09-04	Allow non-unique group IDs in bazel docker containers	Ian Lewis
	Allow non-unique group IDs in the bazel docker container in order to avoid failures using host group IDs that are already present in the image. Issue #801 PiperOrigin-RevId: 267306089
2019-08-16	Bump rules_go to v0.19.3 and bazel_gazelle to v0.18.1.	Nicolas Lacasse
	And bump go toolchain to v1.12.9. Protobuf dependencies must be explicitly included now. PiperOrigin-RevId: 263853370
2019-05-03	gvisor: run bazel in a docker container	Andrei Vagin
	bazel has a lot of dependencies and users don't want to install them just to build gvisor. These changes allows to run bazel in a docker container. A bazel cache is on the local file system (~/.cache/bazel), so incremental builds should be fast event after recreating a bazel container. Here is an example how to build runsc: make BAZEL_OPTIONS="build runsc:runsc" bazel Change-Id: I8c0a6d0c30e835892377fb6dd5f4af7a0052d12a PiperOrigin-RevId: 246570877