If you see the error message:
“Permission denied while trying to connect to the Docker daemon socket at unix”,
it means your user does not have the necessary permissions to interact with Docker. This issue is usually caused by restricted access to the Docker daemon socket file (/var/run/docker.sock).
By default, Docker runs as the root user, and non-root users must have specific permissions to use it. In this guide, we will walk you through step-by-step solutions to fix this error and regain access to Docker.
Why Does This Error Happen?
The “Permission Denied” error occurs due to one of the following reasons:
- Your user is not part of the Docker group.
- The Docker socket file does not have the correct permissions.
- The Docker service is not running or needs a restart.
Now, let’s go through the solutions step by step.
Step 1: Add Your User to the Docker Group
The most common fix is adding your user to the Docker group, which grants the necessary permissions to interact with Docker.
Step 1.1: Check If the Docker Group Exists
Run the following command to check if the Docker group exists:
sudo groupadd docker
If the group already exists, the command will not make any changes.
Step 1.2: Add Your User to the Docker Group
Now, add your user to the Docker group using:
sudo usermod -aG docker $USER
📌 Note: The
$USERvariable refers to the currently logged-in user. If needed, replace$USERwith your actual username.
Step 1.3: Log Out and Log Back In
For the changes to take effect, log out of your session and log back in.
Step 1.4: Verify Your User Is in the Docker Group
After logging back in, check if your user is now part of the Docker group:
groups $USER
If the docker group appears in the output, your user has been added successfully.
Step 2: Check and Fix Docker Socket Permissions
If adding your user to the Docker group doesn’t solve the problem, the Docker socket file (/var/run/docker.sock) may have incorrect permissions.
Step 2.1: Check the Current Permissions
Run the following command to inspect the current permissions of the Docker socket file:
ls -l /var/run/docker.sock
The output should look something like this:
srw-rw---- 1 root docker 0 date time /var/run/docker.sock
This means the root user and the docker group have read and write access.
Step 2.2: Change the File Permissions (If Necessary)
If the docker group does not have the required permissions, you can modify them using:
sudo chmod 660 /var/run/docker.sock
This ensures that the root and docker group have the right permissions.
Step 3: Restart Docker Daemon
If you have made changes to group memberships or file permissions, restarting Docker may be necessary.
sudo systemctl restart docker
This command applies the changes and ensures that Docker is running properly.
Step 4: Verify Docker Is Running
Before testing Docker commands, make sure the Docker service is running:
sudo systemctl status docker
If Docker is not running, start it with:
sudo systemctl start docker
Step 5: Test Docker Without sudo
Now, test whether you can run Docker commands without sudo:
docker ps
If this command works without an error, your issue is resolved! 🚀
Step 6: Use sudo as a Temporary Workaround
If you don’t have time to fix permissions right now, you can temporarily use sudo:
sudo docker ps
However, this is not recommended as a long-term solution.
Step 7: Reboot Your System (Optional)
If logging out and back in did not work, try rebooting your system:
sudo reboot
This refreshes all group memberships and configurations.
Conclusion
The “Permission Denied” error occurs when a non-root user lacks permission to access the Docker daemon. The best solution is to:
✅ Add your user to the Docker group
✅ Check and fix Docker socket permissions
✅ Restart Docker and verify it is running
Using sudo temporarily may work, but it’s best to fix the issue properly. By following these steps, you’ll be able to use Docker smoothly without permission errors! 🚀
This version ensures clarity, proper structure, and SEO optimization, making it easy to follow even for beginners. Let me know if you need any tweaks! 😊