Docker is a platform designed to help developers build, share, and run container applications.
In gVisor, all basic docker commands should function as expected. The host network driver and the bridge network driver are tested and supported.
To run docker within gvisor, runsc must be enable to to allow raw sockets. This
is not the default, --net-raw
must be passed to runsc. To use the following
tutorial, that means having the following configuration in
/etc/docker/daemon.json
:
"runsc": {
"path": "/usr/local/bin/runsc",
"runtimeArgs": [
"--net-raw"
]
}
If you have an existing entry for runsc
, likely created by runsc install
,
then edit the entry and add the "runtimeArgs"
key and value to the existing
entry.
First, prepare a container image with pre-installed Docker:
$ cd images/basic/docker/
$ docker build -t docker-in-gvisor .
Since Docker requires root privileges and a full set of capabilities, a gVisor sandbox needs to be started in privileged mode:
$ docker run --runtime runsc -d --rm --privileged --name docker-in-gvisor docker-in-gvisor
Now, we can build and run Docker containers.
Let’s enter in the gvisor sandbox and run some docker commands:
docker exec -it docker-in-gvisor bash
$ mkdir whalesay && cd whalesay
$ cat > Dockerfile <<EOF
FROM ubuntu
RUN apt-get update && apt-get install -y cowsay curl
RUN mkdir -p /usr/share/cowsay/cows/
RUN curl -o /usr/share/cowsay/cows/docker.cow https://raw.githubusercontent.com/docker/whalesay/master/docker.cow
ENTRYPOINT ["/usr/games/cowsay", "-f", "docker.cow"]
EOF
$ docker build -t whalesay .
....
Successfully tagged whalesay:latest
$ docker run -it --rm whalesay "Containers do not contain, but gVisor-s do!"
_________________________________________
/ Containers do not contain, but gVisor-s \
\ do! /
-----------------------------------------
\ ## .
\ ## ## ## ==
## ## ## ## ===
/""""""""""""""""\___/ ===
~~~ {~~ ~~~~ ~~~ ~~~~ ~~ ~ / ===- ~~~
\______ o __/
\ \ __/
\____\______/