Skip to main content
Docker3 min read2026-03-01

Docker Permission Denied: connect to docker daemon socket

Fix 'Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock'.

Error Code / Stack Trace

Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock

Problem Overview

Non-root Linux users cannot execute docker commands because /var/run/docker.sock is owned by root and the docker group.

Why Does This Happen?

  • The active Linux user account has not been added to the 'docker' user group.
  • The user group membership has not been reloaded in the current terminal session.

Step-by-Step Solution

Step 1: Add current user to the docker group

Grant your non-root user permission to communicate with the Docker daemon.

bash
sudo usermod -aG docker $USER

Step 2: Apply the new group membership

Reload your shell group session without rebooting.

bash
newgrp docker
# Verify with:
docker ps

Common Mistakes to Avoid

  • Prefixing all docker commands with 'sudo', which creates root-owned container bind mount files.

Prevention & Best Practices

  • Consider Docker Rootless mode for enterprise multi-user environments.

Frequently Asked Questions

Do I need to log out of Linux after running usermod?

Yes, group memberships update upon logging out and back in, or immediately within a subshell via 'newgrp docker'.