Docker is no longer accessible without creating a symlink from /run/docker.sock to /var/run/docker.sock
That makes no sense at all because
/var/run is just a link to
$ ls -l /var/run lrwxrwxrwx 1 root root 6 Sep 3 18:14 /var/run -> ../run
Whatever problem you’re having is far more likely to be related to permissions. Try “docker.sock permissions” in your favourite search engine.
For me, this is not the case
sudo ls -l /var/run total 24 -rw-r--r-- 1 root root 5 Sep 19 11:42 crond.pid ---------- 1 root root 0 Sep 19 11:18 cron.reboot drwx------ 7 root root 4096 Sep 19 11:43 docker -rw-r--r-- 1 root root 4 Sep 19 11:43 docker.pid lrwxrwxrwx 1 root root 16 Sep 19 11:58 docker.sock -> /run/docker.sock drwxr-xr-x 3 root root 4096 Sep 19 11:19 expressvpn drwxr-xr-x 2 root $MYUSER 4096 Sep 19 11:16 faillock drwxr-xr-x 4 root root 4096 Sep 19 11:42 NetworkManager
I also tried purging and reinstalling/reconfiguring docker from scratch. Happy to provide other logs as needed, but I don’t believe I have made changes that would result in an actual directory here instead of the symlink like you describe
You must have, because Manjaro sets up
/var/run as a symlink to
/run. This is the upstream default — i.e. from Arch, and from
systemd itself as their upstream.
Strange. Thanks for the comments. I ended up being able to solve this by:
- Stop/Disable/Remove Docker
sudo rm -rf /var/run
/var/runis now a symlink again
ls -al /var/run lrwxrwxrwx 1 root root 6 Sep 19 14:04 /var/run -> ../run
- Reinstall/start/enable Docker. docker.sock is now in
/runand docker commands for the
dockergroup run correctly again.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.