go
/
gvisor
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
gvisor/test
History
Nicolas Lacasse d5002c6adc Allow creating unix domain sockets on the host, behind a flag. 
When enabled with `AllowUDS`, unix domain sockets can be created in the sandbox
and bound on the host filesystem. The application can listen() and accept() on
these sockets as usual. Accept'ed sockets will be donated to the sandbox,
similar to how connect'ed sockets work.

In order to make notifications like poll work, the gofer donates the host-bound
socket FD to the sandbox, but the seccomp filters will (correctly) prevent the
sandbox from calling listen and accept directly on that FD. Instead, listen and
accept calls must go through the gofer. The donated host FD can should only be
used to poll for new incoming connectins.

Note that I changed the order of some of the Lisa RPCs in order to group Bind
with the existing similar Connect method. This changes the RPC numbers in a
backwards-incompatible way, but since nobody is using Lisa yet we are OK. It's
better to make these cleanup changes now before we have users and are locked
in.

PiperOrigin-RevId: 447236441
 		2022-05-07 18:27:18 -07:00
..
benchmarks netstack: switch from sync/atomic to atomicbitops for 32 bit values 2022-04-25 20:41:26 -07:00
cmd/test_app Rename go files that contain "main" function to main.go. 2021-06-09 17:36:51 -07:00
e2e Added integration tests for mounting tmpfs with size option enabled. 2022-04-26 17:00:56 -07:00
fsstress Add fsstress test to goferfs 2021-07-20 22:21:24 -07:00
fuse Allow multiple FUSE filesystems to share a connection. 2022-05-02 11:41:42 -07:00
image Fail tests when container returns non-zero status 2021-04-05 11:39:53 -07:00
iptables Validate flags during install. 2022-02-11 11:24:01 -08:00
kubernetes Make the webhook deterministic. 2022-01-13 15:20:43 -08:00
packetdrill Clean test tags. 2021-04-20 13:11:25 -07:00
packetimpact Automated rollback of changelist 444723128 2022-05-02 21:14:55 -07:00
perf tests: fix compile time warnings 2022-04-29 17:59:14 -07:00
root Add systemd-cgroup support to runsc. 2022-03-17 15:03:44 -07:00
runner Enable all tests for lisafs. 2022-03-10 10:09:05 -08:00
runtimes Update runtime tests documentation with new versions. 2022-04-21 11:27:57 -07:00
syscalls Allow creating unix domain sockets on the host, behind a flag. 2022-05-07 18:27:18 -07:00
uds Allow creating unix domain sockets on the host, behind a flag. 2022-05-07 18:27:18 -07:00
util cgroupfs: Fix test race with task exit. 2022-04-27 14:06:51 -07:00
BUILD Standardize on tools directory. 2020-01-27 12:21:00 -08:00
README.md Add systemd-cgroup support to runsc. 2022-03-17 15:03:44 -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:

make docker-tests

To run root tests, run:

make sudo TARGETS=test/root:root_test

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.