Cannot connect to the docker daemon
Hi everyone - can't figure out what's going on here. I have runtipi installed, am running multiple containers, and they all work fine, but when I try to do anything CLI-based like update tipi or enter a container console/log I get this error:
Cannot connect to the Docker daemon at unix:///home/jack/.docker/desktop/docker.sock. Is the docker daemon running?
I don't understand how my whole server setup could be working fine if it wasn't running, so maybe this is a user permissions issue? When I use systemctl to list processes it says the Docker service is running (see attached). The specific thing I'd like to do is use docker exec to install HACS for Home Assistant. If anyone can help me figure out what's going on I'd appreciate it.
16 Replies
Have you tried using sudo?
I'm using sudo when I do docker commands, still get the error. I can try sudoing my systemctl checks and see if I get more info
How did you install docker?
I used to have Docker Desktop on this machine but I uninstalled it and then installed runtipi with the install command
could it be looking in the wrong place for an old version of the daemon?
Are you sure you didn't use snap or that docker was completely uninstalled before installing runtipi
I guess I'm not 100% sure. I don't think I used a snap because I installed everything via CLI
Can you share the output of
docker -vversion 28.2.2, build e6534b4
Alright can you try
sudo docker psYep that lists all my tipi containers and their uptime. I can screenshot the whole output if that'd help
Oh
Didn't notice the original output
Seems like docker is trying to connect to a local socket
Leftover from docker desktop
Normally the socket should be at /var/run/docker.sock
Try
docker context use default
And then try to do docker psHm yeah that file seems to not be there
ps gives me the same list as before, everything is up and healthy
Ok try to use the CLI now
With sudo
Looks like it's doing something
before it would throw an error on step 2 so I think this is working
It's taking a while to restart the containers but the initial problem is solved. Thanks a bunch! none of the google results hinted at the context-default thing
You probably should be able to do
docker context ls and remove everything with docker context rm except the default one