gvisor - Container Runtime Sandbox

Age	Commit message (Collapse)	Author
2020-11-17	Add support for TTY in multi-container	Fabricio Voznika
	Fixes #2714 PiperOrigin-RevId: 342950412
2020-10-05	Enable more VFS2 tests	Fabricio Voznika
	Updates #1487 PiperOrigin-RevId: 335516732
2020-09-17	[testing] Use container address to talk to server running inside container.	Ayush Ranjan
	Docker does not have IPv6 port forwarding as tracked by the following issue: https://github.com/moby/moby/issues/11518 So when running bazel itself inside a docker container, we can not use the host port bindings to communicate with sockets inside the container. This was causing integration tests and image tests to fail when run through our Makefile targets. PiperOrigin-RevId: 332355051
2020-08-26	Make flag propagation automatic	Fabricio Voznika
	Use reflection and tags to provide automatic conversion from Config to flags. This makes adding new flags less error-prone, skips flags using default values (easier to read), and makes tests correctly use default flag values for test Configs. Updates #3494 PiperOrigin-RevId: 328662070
2020-08-20	Use a explicit random src for RandomID.	Bhasker Hariharan
	PiperOrigin-RevId: 327659759
2020-08-19	Move boot.Config to its own package	Fabricio Voznika
	Updates #3494 PiperOrigin-RevId: 327548511
2020-08-10	Speed up iptables tests	Kevin Krakauer
	//test/iptables:iptables_test runs 30 seconds faster on my machine. * Using contexts instead of many smaller timeouts makes the tests less likely to flake and removes unnecessary complexity. * We also use context to properly shut down concurrent goroutines and the test container. * Container logs are always logged.
2020-07-13	Merge pull request #2672 from amscanne:shim-integrated	gVisor bot
	PiperOrigin-RevId: 321053634
2020-07-08	Enable shards in runtime test runner.	Ayush Ranjan
	Fixed an issue with the runtime test runner which enables us to run tests in shards. We had to touch the status file as indicated by an env var. PiperOrigin-RevId: 320236205
2020-06-11	Set the HOME environment variable for sub-containers.	Ian Lewis
	Fixes #701 PiperOrigin-RevId: 316025635
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-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