How to fix Docker daemon permission denied, docker.sock access denied in Kubernetes

KubernetesBEGINNERCRITICALUpdated Dec 6, 2025· 136 views

Container runtime socket access denied. Fix by adding kubelet user to docker group, fixing socket permissions, or using rootless Docker.

Quick fix

Fixes DOCKER_PERMISSION_DENIED

sudo usermod -aG docker kubelet
  1. Add kubelet user to docker group
  2. Restart kubelet
  3. Check socket permissions
  4. Verify node is Ready
kubernetes — error
sudo usermod -aG docker kubelet
Docker daemon permission denied, docker.sock access denied

What this error means

The kubelet (or container runtime) can't access the Docker daemon socket due to insufficient permissions. This prevents pod creation.

Typical symptoms

  • Node status shows NotReady
  • kubelet fails to create pods
  • Permission denied errors in kubelet logs
  • Socket file inaccessible

Common causes

  1. kubelet user not in docker group
  2. Docker socket has restrictive permissions
  3. SELinux blocking access

How to fix "Docker daemon permission denied, docker.sock access denied"

1Add kubelet user to docker group
bash
sudo usermod -aG docker kubelet
2Restart kubelet
bash
sudo systemctl restart kubelet
3Check socket permissions
bash
ls -la /var/run/docker.sock
4Verify node is Ready
bash
kubectl get nodes
5Use rootless Docker if needed

Consider rootless mode for better security.

Advanced notes

Never change socket permissions directly. Always use group membership.

Frequently asked questions

What does "DOCKER_PERMISSION_DENIED" mean?
The kubelet (or container runtime) can't access the Docker daemon socket due to insufficient permissions. This prevents pod creation.
How do I fix "DOCKER_PERMISSION_DENIED"?
Container runtime socket access denied. Fix by adding kubelet user to docker group, fixing socket permissions, or using rootless Docker.
What causes "DOCKER_PERMISSION_DENIED"?
kubelet user not in docker group Docker socket has restrictive permissions SELinux blocking access
Is the "DOCKER_PERMISSION_DENIED" error serious?
Yes. This is a critical-severity error that usually blocks work until it is fixed, but the steps above resolve it.

Official resources & further reading