go
/
gvisor
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
gvisor/test
History
Adin Scannell c60613475c Standardize all Docker images. 
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-24 14:11:42 -07:00
..
cmd/test_app Simplify Docker test infrastructure. 2020-04-23 11:33:30 -07:00
e2e Simplify Docker test infrastructure. 2020-04-23 11:33:30 -07:00
image Simplify Docker test infrastructure. 2020-04-23 11:33:30 -07:00
iptables Standardize all Docker images. 2020-04-24 14:11:42 -07:00
packetdrill Standardize all Docker images. 2020-04-24 14:11:42 -07:00
packetimpact Standardize all Docker images. 2020-04-24 14:11:42 -07:00
perf Deflake //third_party/gvisor/test/perf:getdents_benchmark_runsc_ptrace 2020-04-03 12:29:03 -07:00
root Standardize all Docker images. 2020-04-24 14:11:42 -07:00
runner Simplify Docker test infrastructure. 2020-04-23 11:33:30 -07:00
runtimes Standardize all Docker images. 2020-04-24 14:11:42 -07:00
syscalls tcp: handle listen after shutdown properly 2020-04-22 14:17:11 -07:00
uds Standardize on tools directory. 2020-01-27 12:21:00 -08:00
util Add missing newline 2020-04-03 11:38:37 -07:00
BUILD Standardize on tools directory. 2020-01-27 12:21:00 -08:00
README.md Add more instructions to test/README.md 2019-10-18 16:18:52 -07:00

README.md

Tests

The tests defined under this path are verifying functionality beyond what unit tests can cover, e.g. integration and end to end tests. Due to their nature, they may need extra setup in the test machine and extra configuration to run.

  • syscalls: system call tests use a local runner, and do not require additional configuration in the machine.
  • integration: defines integration tests that uses docker run to test functionality.
  • image: basic end to end test for popular images. These require the same setup as integration tests.
  • root: tests that require to be run as root. These require the same setup as integration tests.
  • util: utilities library to support the tests.

For the above noted cases, the relevant runtime must be installed via runsc install before running. Just note that they require specific configuration to work. This is handled automatically by the test scripts in the scripts directory and they can be used to run tests locally on your machine. They are also used to run these tests in kokoro.

Example:

To run image and integration tests, run:

./scripts/docker_test.sh

To run root tests, run:

./scripts/root_test.sh

There are a few other interesting variations for image and integration tests:

  • overlay: sets writable overlay inside the sentry
  • hostnet: configures host network pass-thru, instead of netstack
  • kvm: runsc the test using the KVM platform, instead of ptrace

The test will build runsc, configure it with your local docker, restart dockerd, and run tests. The location for runsc logs is printed to the output.