diff options
| author | Andrei Vagin <avagin@google.com> | 2019-05-03 14:11:55 -0700 |
|---|---|---|
| committer | Shentubot <shentubot@google.com> | 2019-05-03 14:13:08 -0700 |
| commit | 9e1c253fe814c85a316520bd6bd258adaa71df79 (patch) | |
| tree | 688af9574f7d71aa144c1ba0c74b416542edbb0f /README.md | |
| parent | 24d8656585e6072ff7d5a00a7eb4bd25cba42dc4 (diff) | |
gvisor: run bazel in a docker container
bazel has a lot of dependencies and users don't want to install them
just to build gvisor.
These changes allows to run bazel in a docker container.
A bazel cache is on the local file system (~/.cache/bazel), so
incremental builds should be fast event after recreating a bazel
container.
Here is an example how to build runsc:
make BAZEL_OPTIONS="build runsc:runsc" bazel
Change-Id: I8c0a6d0c30e835892377fb6dd5f4af7a0052d12a
PiperOrigin-RevId: 246570877
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 15 |
1 files changed, 15 insertions, 0 deletions
@@ -70,6 +70,14 @@ bazel build runsc sudo cp ./bazel-bin/runsc/linux_amd64_pure_stripped/runsc /usr/local/bin ``` +If you don't want to install bazel on your system, you can build runsc in a +Docker container: + +``` +make runsc +sudo cp ./bazel-bin/runsc/linux_amd64_pure_stripped/runsc /usr/local/bin +``` + ### Testing The test suite can be run with Bazel: @@ -78,6 +86,13 @@ The test suite can be run with Bazel: bazel test ... ``` +or in a Docker container: + +``` +make unit-tests +make tests +``` + ### Using remote execution If you have a [Remote Build Execution][rbe] environment, you can use it to speed |