From 09bb1646db6623095380f9618283cb11a8d2ba7e Mon Sep 17 00:00:00 2001 From: Spencer Killen Date: Tue, 21 Mar 2023 11:42:27 -0600 Subject: [PATCH] Add 'DockerHelp.md' --- DockerHelp.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 DockerHelp.md diff --git a/DockerHelp.md b/DockerHelp.md new file mode 100644 index 0000000..1fe2df2 --- /dev/null +++ b/DockerHelp.md @@ -0,0 +1,13 @@ +If you get permission errors when running `docker version`, follow these instructions (on Linux) to give yourself permissions +1. Run `stat /var/run/docker.sock` to see the permissions for the docker socket (The file path is printed out when you get a permission error, yours may be different). You should see a line like +``` +Access: (0660/srw-rw----) Uid: ( 0/ root) Gid: ( 1003/ root) +``` +The above tells you that the docker socket belongs to the group with GID 1003 (root) and that the group has neither read nor write permissions. +2. Change the socket's group to be yours with `sudo chgrp "$USER" /var/run/docker.sock`. Confirm this change by running `stat` again. +3. Give the group read and write privileges with `sudo chmod g+rw /var/run/docker.sock` +4. Confirm that you can run `docker version` without permission errors. + + + +- (Alternative approach for multiuser systems which requires logging out and back in again)[https://stackoverflow.com/questions/48957195/how-to-fix-docker-got-permission-denied-issue] \ No newline at end of file