gvisor - Container Runtime Sandbox

Age	Commit message (Collapse)	Author
2020-10-05	Remove reference to deleted script	Kevin Krakauer
	PiperOrigin-RevId: 335516625
2020-04-23	Simplify Docker test infrastructure.	Adin Scannell
	This change adds a layer of abstraction around the internal Docker APIs, and eliminates all direct dependencies on Dockerfiles in the infrastructure. A subsequent change will automated the generation of local images (with efficient caching). Note that this change drops the use of bazel container rules, as that experiment does not seem to be viable. PiperOrigin-RevId: 308095430
2020-02-10	iptables: add instructions for runsc building.	Kevin Krakauer
	The readme didn't mention that users need to: - `bazel build` when working on iptables tests - enable raw sockets in /etc/docker/daemon.json. PiperOrigin-RevId: 294260169
2020-02-06	Fix `bazel run` target in docs.	Kevin Krakauer
	PiperOrigin-RevId: 293676954
2020-01-29	Fix iptables tests that were broken by rename.	Kevin Krakauer
	The name of the runner binary target changed from "runner" to "runner-image", causing iptables tests to fail. PiperOrigin-RevId: 292242263
2020-01-06	Fix readme formatting.	Kevin Krakauer
	PiperOrigin-RevId: 288402480
2019-12-12	Add iptables testing framework.	Kevin Krakauer
	It would be preferrable to test iptables via syscall tests, but there are some problems with that approach: * We're limited to loopback-only, as syscall tests involve only a single container. Other link interfaces (e.g. fdbased) should be tested. * We'd have to shell out to call iptables anyways, as the iptables syscall interface itself is too large and complex to work with alone. * Running the Linux/native version of the syscall test will require root, which is a pain to configure, is inherently unsafe, and could leave host iptables misconfigured. Using the go_test target allows there to be no new test runner. PiperOrigin-RevId: 285274275