Skip to content

Commit a6227bd

Browse files
wglambertyosifkittianon
authored
Add some notes to the Rootless section (#1884)
Co-authored-by: yosifkit <[email protected]> Co-authored-by: Tianon Gravi <[email protected]>
1 parent 64f8891 commit a6227bd

File tree

1 file changed

+15
-0
lines changed

1 file changed

+15
-0
lines changed

docker/content.md

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -209,6 +209,21 @@ Some of these will not be supported based on the settings on the host's `dockerd
209209

210210
For more information about using the experimental "rootless" image variants, see [docker-library/docker#174](https://github.com/docker-library/docker/pull/174).
211211

212+
**Note:** just like the regular `dind` images, `--privileged` is required for Docker-in-Docker to function properly ([docker-library/docker#151](https://github.com/docker-library/docker/issues/151#issuecomment-483185972) & [docker-library/docker#281](https://github.com/docker-library/docker/issues/281#issuecomment-744766015)). For `19.03.x` rootless images, an argument of `--experimental` is required for `dockerd` ([docker/docker#40759](https://github.com/docker/docker/pull/40759)).
213+
214+
Basic example usage:
215+
216+
```console
217+
$ docker run -d --name some-docker --privileged docker:dind-rootless
218+
$ docker logs --tail=3 some-docker # to verify the daemon has finished generating TLS certificates and is listening successfully
219+
time="xxx" level=info msg="Daemon has completed initialization"
220+
time="xxx" level=info msg="API listen on /run/user/1000/docker.sock"
221+
time="xxx" level=info msg="API listen on [::]:2376"
222+
$ docker exec -it some-docker docker-entrypoint.sh sh # using "docker-entrypoint.sh" which auto-sets "DOCKER_HOST" appropriately
223+
/ $ docker info --format '{{ json .SecurityOptions }}'
224+
["name=seccomp,profile=default","name=rootless"]
225+
```
226+
212227
## Where to Store Data
213228

214229
Important note: There are several ways to store data used by applications that run in Docker containers. We encourage users of the `%%REPO%%` images to familiarize themselves with the options available, including:

0 commit comments

Comments
 (0)