Docker client tries to connect to the wrong sock file

Bug #2020890 reported by Bartosz Woronicz
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
docker.io (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

That is true for both apt package and snap

it should /run/docker.sock instead of /var/run/docker.sock

$ docker ps
Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get "http://%2Fvar%2Frun%2Fdocker.sock/v1.24/containers/json": dial unix /var/run/docker.sock: connect: permission denied

$ apt show docker.io
Package: docker.io
Version: 20.10.21-0ubuntu1~22.04.3
Built-Using: glibc (= 2.35-0ubuntu3), golang-1.18 (= 1.18.1-1ubuntu1.1)
Priority: optional
Section: universe/admin
Origin: Ubuntu

$ snap info docker |grep installed
installed: 20.10.24 (2893) 135MB -

Revision history for this message
Dimitri John Ledkov (xnox) wrote :

does this work?

sudo snap run --shell docker.docker

$ ls -latr /var/run /run/docker.sock /var/run/docker.sock
lrwxrwxrwx 1 root root 4 Mar 25 04:54 /var/run -> /run
srw-rw---- 1 root docker 0 May 24 09:07 /var/run/docker.sock
srw-rw---- 1 root docker 0 May 24 09:07 /run/docker.sock

if yes, does it not work without sudo?

Is so, is your user in the docker group, and have you relogged in after adding userself to the docker group?

Changed in docker.io (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for docker.io (Ubuntu) because there has been no activity for 60 days.]

Changed in docker.io (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.