Skip to content

Document limitations of docker-in-gvisor #12146

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Document limitations of docker-in-gvisor #12146

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions g3doc/user_guide/tutorials/docker-in-gvisor.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,16 @@ applications.
In gVisor, all basic docker commands should function as expected. The host
network driver and the bridge network driver are tested and supported.

### Limitations

- `dockerd` inside gVisor needs to be executed with flags
`--iptables=false --ip6tables=false` and additional network setup is needed, check
[images/basic/docker/start-dockerd.sh](https://github.com/google/gvisor/blob/master/images/basic/docker/start-dockerd.sh)
for the reference
- because iptables disabled, `docker run --expose=` does not expose the port;
if a nested container needs to expose ports, inside gVisor use `docker run --network=host`
- docker 28 may not work

### NOTE on runsc setup

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