go
/
gvisor
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
gvisor/Dockerfile

10 lines
313 B
Docker
Raw Normal View History

arm64: add a travis build ci Build runsc and run "runsc do ls". Signed-off-by: Andrei Vagin <avagin@gmail.com>
2019-11-12 04:26:38 +00:00
FROM fedora:31
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 21:11:55 +00:00
arm64: add a travis build ci Build runsc and run "runsc do ls". Signed-off-by: Andrei Vagin <avagin@gmail.com>
2019-11-12 04:26:38 +00:00
RUN dnf install -y dnf-plugins-core && dnf copr enable -y vbatts/bazel
Packetimpact in Go with c++ stub PiperOrigin-RevId: 301382690
2020-03-17 15:52:14 +00:00
RUN dnf install -y bazel2 git gcc make golang gcc-c++ glibc-devel python3 which python3-pip python3-devel libffi-devel openssl-devel pkg-config glibc-static libstdc++-static patch
arm64: add a travis build ci Build runsc and run "runsc do ls". Signed-off-by: Andrei Vagin <avagin@gmail.com>
2019-11-12 04:26:38 +00:00
RUN pip install pycparser
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 21:11:55 +00:00
WORKDIR /gvisor