gvisor - Container Runtime Sandbox

Age	Commit message (Collapse)	Author
2020-01-27	Standardize on tools directory.	Adin Scannell
	PiperOrigin-RevId: 291745021
2020-01-23	Try running kythe build on RBE.	Brad Burlage
	Also add our RBE project/instance to the --config=remote defaults. PiperOrigin-RevId: 291201426
2019-12-06	Build with C++17	Michael Pratt
	This will require a reasonably modern toolchain. I've put minimum compiler versions in the README based on versions in https://en.cppreference.com/w/cpp/compiler_support that have mostly complete language and library support. The minimum Bazel version bump is unrelated, but 0.28 is definitely not supported anymore. Please report issues on gvisor.dev/issue/1349. Fixes #1349 PiperOrigin-RevId: 284274250
2019-09-10	Fix `runsc --version` and add a test.	Nicolas Lacasse
	We need to include the `--stamp` flag in `tools/workspace_status.sh` for the version to be picked up by the linker. Not sure why. Also changes the VERSION string to STABLE_VERSION, which will cause the program to be re-linked if the string changes. Fixes #830
2019-08-13	Bump Bazel to v0.28.0	Nicolas Lacasse
	The new version has a change in behavior when using a custom platform: * Old behavior: rules that don't require a toolchain used host_platform, no matter what execution platforms are specified. * New behavior: rules that don't require a toolchain use standard platform resolution that starts with execution platforms. As part of this change, we cannot use the "extra_exectution_platforms" flag provided by the default bazelrc. I got rid of the default bazelrc file, and made our custom .bazelrc as minimal as possible. PiperOrigin-RevId: 263176802
2019-06-03	Update straggling copyright holder	Michael Pratt
	Updates #209 PiperOrigin-RevId: 251289513
2019-04-05	Make it easier for humans to use RBE, and maintain our bazelrc.	Nicolas Lacasse
	This CL merges all RBE-specific configuration from .bazelrc_rbe into .bazelrc so that it will be picked up by default by users running bazel. It also checks in a bazelrc from the upstream bazel-toolchains repository, and imports that into our repo-specific .bazelrc. This makes it easier to maintain and update the bazelrc going forward. Documentation was added to the README. PiperOrigin-RevId: 242208733 Change-Id: Iea32de9be85b024bd74f88909b56b2a8ab34851a
2018-11-06	Move bazelrc to new location	Michael Pratt
	Bazel 0.18 moved the workspace bazelrc location from //tools/bazel.rc to //.bazelrc. The old location will be dropped by a future version of bazel. This bumps the minimum required version of bazel to 0.18. More context: https://groups.google.com/forum/#!msg/bazel-discuss/ycDacctX2vw/EGFxGLibAgAJ PiperOrigin-RevId: 220338084 Change-Id: Ib6fa83a4a0f89e8e898d67152c7bd429e0b9b21e