Adding upstream version 1.16.0.upstream/1.16.0

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

1 files changed, 22 insertions, 4 deletions

diff --git a/packaging/docker/README.md b/packaging/docker/README.md
index 6ae299f1d..0bf416cd4 100644
--- a/packaging/docker/README.md
+++ b/packaging/docker/README.md
@@ -54,10 +54,28 @@ services:
 
 ### Docker container names resolution
 
-If you want to have your container names resolved by netdata it needs to have access to docker group. To achive that just add environment variable `PGID=999` to netdata container, where `999` is a docker group id from your host. This number can be found by running:
-```bash
-grep docker /etc/group | cut -d ':' -f 3
-```
+If you want to have your container names resolved by netdata, you need to do two things:
+1) Make netdata user be part of the group that owns the socket.
+   To achieve that just add environment variable `PGID=[GROUP NUMBER]` to the netdata container,
+   where `[GROUP NUMBER]` is practically the group id of the group assigned to the docker socket, on your host.
+   This group number can be found by running the following (if socket group ownership is docker):
+   ```bash
+   grep docker /etc/group | cut -d ':' -f 3
+   ```
+
+2) Change docker socket access level to read/write like so:
+   from
+   ```
+   /var/run/docker.sock:/var/run/docker.sock:ro
+   ```
+
+   change to
+   ```
+   /var/run/docker.sock:/var/run/docker.sock:rw
+   ```
+
+**Important Note**: You should seriously consider the necessity of activating this option,
+as it grants to the netdata user access to the privileged socket connection of docker service
 
 ### Pass command line options to Netdata