summaryrefslogtreecommitdiffhomepage
path: root/Dockerfile
diff options
context:
space:
mode:
authorAndrei Vagin <avagin@google.com>2019-05-03 14:11:55 -0700
committerShentubot <shentubot@google.com>2019-05-03 14:13:08 -0700
commit9e1c253fe814c85a316520bd6bd258adaa71df79 (patch)
tree688af9574f7d71aa144c1ba0c74b416542edbb0f /Dockerfile
parent24d8656585e6072ff7d5a00a7eb4bd25cba42dc4 (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 'Dockerfile')
-rw-r--r--Dockerfile8
1 files changed, 8 insertions, 0 deletions
diff --git a/Dockerfile b/Dockerfile
new file mode 100644
index 000000000..32ac76f1b
--- /dev/null
+++ b/Dockerfile
@@ -0,0 +1,8 @@
+FROM ubuntu:bionic
+
+RUN apt-get update && apt-get install -y curl gnupg2 git
+RUN echo "deb [arch=amd64] http://storage.googleapis.com/bazel-apt stable jdk1.8" | tee /etc/apt/sources.list.d/bazel.list && \
+ curl https://bazel.build/bazel-release.pub.gpg | apt-key add -
+RUN apt-get update && apt-get install -y bazel && apt-get clean
+
+WORKDIR /gvisor