You are not logged in.
Pages: 1
Topic closed
When running
> sudo docker run hello-worldI get the welcome message. However, if I run
> docker run hello-worldI get
docker: Cannot connect to the Docker daemon at unix:///home/d/.docker/desktop/docker.sock. Is the docker daemon running?Online forums suggested that is could be a permission issue. However, if I run
> groups $USERI get
wheel docker dSo it appears like I am in the proper group. What else could be the issue?
Offline
Is the docker daemon running? The user group is only relevant so you can actually connect to the instance assuming it's running. Output of
systemctl status docker? did you reboot/restart docker after adding your user to the group? I also wonder why it tries to connect to a user local socket here...
Last edited by V1del (2025-01-22 14:46:25)
Offline
It says that it is "active (running)". Why would it not? Docker works with sudo. Is it possible for it to work with sudo if the docker daemon is not running?
I just rebooted my laptop, and that did not fix the issue.
Offline
the main question is why it tries to look at your home dir instead of the socket file /var/run/docker.sock which would allow you access. Are you exporting some env variable or so?
printenvOffline
running
env DOCKER_HOST=unix:///var/run/docker.sock docker psworks. Normally DOCKER_HOST is not defined
Offline
feels like a docker CLI bug, it should look there by default (or at least try to look there after $HOME/.docker failed) instead of randomly guessing something in your $HOME dir.
Offline
I'll report it in their forums. Thanks
Offline
After installing Docker with the official (experimental) Docker Desktop and failing the binary installation, I encountered a similar issue, as I had two Docker contexts despite the failed installation process.
docker context ls
docker context use default
docker context rm desktop-linuxOffline
After installing Docker with the official (experimental) Docker Desktop and failing the binary installation, I encountered a similar issue, as I had two Docker contexts despite the failed installation process.
docker context ls docker context use default docker context rm desktop-linux
Having multiple contexts, especially as above, was the issue for me - since it seems nobody replied to confirm this.
Thank you!
Offline
Mod note: Closing this old thread.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Online
Pages: 1
Topic closed