From 720a6a823987967a9fd6a7918907b271f8dbee55 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Pawe=C5=82=20Gronowski?= Date: Thu, 29 Dec 2022 14:33:34 +0100 Subject: [PATCH] docs/run: Fix url to blog "Docker can now run within Docker" MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Paweł Gronowski --- docs/reference/run.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/reference/run.md b/docs/reference/run.md index 767e441ee4..c3628e45cc 100644 --- a/docs/reference/run.md +++ b/docs/reference/run.md @@ -1254,7 +1254,7 @@ executes `docker run --privileged`, Docker will enable access to all devices on the host as well as set some configuration in AppArmor or SELinux to allow the container nearly all the same access to the host as processes running outside containers on the host. Additional information about running with `--privileged` -is available on the [Docker Blog](https://blog.docker.com/2013/09/docker-can-now-run-within-docker/). +is available on the [Docker Blog](https://www.docker.com/blog/docker-can-now-run-within-docker/). If you want to limit access to a specific device or devices you can use the `--device` flag. It allows you to specify one or more devices that