Skip to content

Commit 6ae080e

Browse files
committed
Document limitations of docker-in-gvisor
1 parent 2925932 commit 6ae080e

File tree

1 file changed

+10
-0
lines changed

1 file changed

+10
-0
lines changed

g3doc/user_guide/tutorials/docker-in-gvisor.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,16 @@ applications.
66
In gVisor, all basic docker commands should function as expected. The host
77
network driver and the bridge network driver are tested and supported.
88

9+
### Limitations
10+
11+
- `dockerd` inside gVisor needs to be executed with flags
12+
`--iptables=false --ip6tables=false` and additional network setup is needed, check
13+
[images/basic/docker/start-dockerd.sh](https://github.com/google/gvisor/blob/master/images/basic/docker/start-dockerd.sh)
14+
for the reference
15+
- because iptables disabled, `docker run --expose=` does not expose the port;
16+
if a nested container needs to expose ports, inside gVisor use `docker run --network=host`
17+
- docker 28 may not work ([#11883](https://github.com/google/gvisor/issues/11883))
18+
919
### NOTE on runsc setup
1020

1121
To run docker within gvisor, runsc must be enabled to allow raw sockets. This is

0 commit comments

Comments
 (0)