12 August 2026 · 2 min read
Add your Linux user to the docker group so the CLI can talk to the daemon without prefixing every command with sudo.
Keep reading
Journal list
After installing Docker Engine, every docker call needs sudo unless your user can open the Docker socket. The usual fix on Ubuntu is membership in the docker group.
The Docker daemon listens on a Unix socket owned by root:docker. Unprivileged users cannot connect, which is intentional: anyone who can talk to that socket can mount host paths and effectively become root.
sudo usermod -aG docker "$USER"
To add a different account:
sudo usermod -aG docker otherusername
Group changes apply on the next login session. Either:
su - "$USER", ornewgrp dockerConfirm:
groups
# expect: … docker …
docker run --rm hello-world
Treat the docker group like sudo. On shared or production hosts, prefer rootless Docker, dedicated CI agents, or tightly scoped SSH users instead of broad group membership.
| Symptom | Likely fix |
|---|---|
permission denied while trying to connect to the Docker daemon socket | Group not applied — re-login or newgrp docker |
| Daemon not running | sudo systemctl start docker |
| Works with sudo only | id / groups still missing docker |
Once the group is active, drop sudo from day-to-day docker and docker compose commands on that machine.