June
e83b6ff318
Document issue with containers on user-defined bridges and using the gVisor runsc runtime. Also provide a helper resolv.conf as a workaround.
26 lines
1.1 KiB
Markdown
26 lines
1.1 KiB
Markdown
# Role `docker`
|
|
|
|
Ensures the Docker Engine and other related packages are installed from the Docker repos.
|
|
For detailed list of packages see: [`tasks/main/02_docker_install.yaml`](./tasks/main/02_docker_install.yaml).
|
|
|
|
## Supported Distributions
|
|
|
|
The following distributions are supported:
|
|
|
|
- Debian 11
|
|
- Debian 12
|
|
|
|
## Required Arguments
|
|
|
|
None.
|
|
|
|
## Optional Arguments
|
|
|
|
- `docker__gvisor_setup`: Whether or not to set up [gVisor](https://gvisor.dev/) (`runsc` runtime).
|
|
> Note: gVisor doesn't work with the embedded DNS server Docker forces for user-defined bridges (see the [relevant GitHub issue](https://github.com/google/gvisor/issues/7469)). A workaround would be to bind mount a `resolv.conf` not relying on localhost DNS (note however that this still doesn't provide local container name resolution). When enabling this option such a helper `resolv.conf` pointing to Quad9 gets deployed to `/etc/gvisor-helper-resolv.conf` for bind-mounting. See the file for usage instructions.
|
|
|
|
Defaults to `false`.
|
|
|
|
## Links & Resources
|
|
|
|
- <https://docs.docker.com/engine/install/debian/>
|