Ubuntu 20.04 Docker permission denied for non-root user

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution – Primary Fix
7. Solution – Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

Docker commands fail for standard users with socket permission denied messages.

Environment & Reproduction

The docker daemon works under sudo but fails in regular shell sessions.

Root Cause Analysis

User not in docker group, stale session group cache, or incorrect socket ownership.

Quick Triage

Check group membership and daemon status before editing Docker service configuration.

Step-by-Step Diagnosis

Run id, groups, ls -l /var/run/docker.sock, and systemctl status docker.

Solution – Primary Fix

Add user to docker group, relogin to refresh groups, and verify socket permissions.

Solution – Alternative Approaches

Use rootless Docker mode for tighter security boundaries where suitable.

Verification & Acceptance Criteria

docker ps and container lifecycle commands run successfully without sudo.

Rollback Plan

Remove user from docker group and restore previous daemon access model if needed.

Prevention & Hardening

Document least-privilege access policy and audit docker group membership regularly.

Related Errors & Cross-Refs

Associated with cgroup configuration issues and service startup failures on kernel updates.

Related tutorial: View the step-by-step tutorial for Ubuntu 20.04 LTS.

View all Ubuntu 20.04 LTS tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Refer to Docker Engine Linux post-install steps and Ubuntu container runtime docs.