Skip to main content
FA
FreeToolAlt.dev

Save money without sacrificing quality

GitHub
Back to docker
dockerbeginnerpermissionsVerified

Docker Permission Denied: Causes and Fixes

Last reviewed: 9/14/2026
3 solutions

Exact Error Message

permission denied while trying to connect to the Docker daemon socket

Quick Fix

Add user to docker group: sudo usermod -aG docker $USER and then log out and back in.

What This Error Means

Docker daemon runs as root and the socket is owned by root. Regular users need to be added to the docker group to access Docker without sudo.

Common Symptoms
  • •Cannot run docker commands without sudo
  • •Permission denied error
  • •Cannot access Docker daemon
Common Causes
  • •User not in docker group
  • •Docker daemon not running
  • •Socket permissions incorrect
  • •User session not refreshed after group change
Diagnostic Steps
  1. 1Check if docker group exists: getent group docker
  2. 2Check if user is in docker group: groups $USER
  3. 3Check docker socket permissions: ls -la /var/run/docker.sock
  4. 4Verify docker daemon is running: sudo systemctl status docker

Solutions

Solution 1: Add user to docker group
  1. 1Add current user to docker group
  2. 2Log out and log back in to refresh group membership
  3. 3Verify docker works without sudo
  4. 4Test with docker ps

Commands to Run

You must log out and back in for group changes to take effect

sudo usermod -aG docker $USER

Never grant docker group access to untrusted users

newgrp docker
docker ps
Solution 2: Start Docker daemon
  1. 1Check if Docker daemon is running
  2. 2Start Docker daemon if stopped
  3. 3Enable Docker to start on boot
  4. 4Verify daemon status

Commands to Run

Requires sudo or root access

sudo systemctl start docker
sudo systemctl enable docker
sudo systemctl status docker
Solution 3: Fix socket permissions
  1. 1Check current socket permissions
  2. 2Adjust socket ownership if needed
  3. 3Restart Docker daemon
  4. 4Verify permissions

Commands to Run

Incorrect permissions can break Docker

sudo chown root:docker /var/run/docker.sock

Requires sudo access

sudo chmod 660 /var/run/docker.sock
Prevention Tips
  • ✓Add trusted users to docker group
  • ✓Use sudo for sensitive operations
  • ✓Monitor docker group membership
  • ✓Keep Docker daemon updated
  • ✓Use rootless Docker when possible

Version Notes: Applies to Docker 20.10+ on Linux

Official Documentation
Related Errors
Docker Port Is Already Allocated: Causes and Fixes
Docker cannot bind to a port because another process or container is already using it.
GitHub Actions Permission Denied: Causes and Fixes
GitHub Actions workflow fails due to insufficient permissions or authentication issues.
Linux Permission Denied: Causes and Fixes
User lacks necessary permissions to execute a file, access a directory, or perform an operation.
Kubernetes ImagePullBackOff: Causes and Fixes
Kubernetes cannot pull the container image from the registry.

Was this helpful?