go
/
gvisor
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
2,301 Commits 2 Branches 96 Tags 81 MiB
Commit Graph

4 Commits

Author SHA1 Message Date
Ian Lewis 7ac46c5048 Allow non-unique UIDs in bazel docker containers 
Allow non-unique UIDs in the bazel docker container in order to avoid failures
using host UIDs that are already present in the image.

Issue #1267

PiperOrigin-RevId: 283456369
 2019-12-02 18:00:33 -08:00
Ian Lewis e31686500d Allow non-unique group IDs in bazel docker containers 
Allow non-unique group IDs in the bazel docker container in order to avoid
failures using host group IDs that are already present in the image.

Issue #801

PiperOrigin-RevId: 267306089
 2019-09-04 23:20:12 -07:00
Nicolas Lacasse d60d99cb61 Bump rules_go to v0.19.3 and bazel_gazelle to v0.18.1. 
And bump go toolchain to v1.12.9.

Protobuf dependencies must be explicitly included now.

PiperOrigin-RevId: 263853370
 2019-08-16 15:02:11 -07:00
Andrei Vagin 9e1c253fe8 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
 2019-05-03 14:13:08 -07:00