Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

1.3.0, docker.socket file is a link to a file that does not exist

See original GitHub issue

Actual Behavior

since the update to version 1.3.0, docker stopped working

I think the reason is, that now the socker file is a link to a file that does not exist

Steps to Reproduce

docker ps

Result

error during connect: Get "http://%2Fvar%2Frun%2Fdocker.sock/v1.24/containers/json": EOF

Expected Behavior

docker shows images

Additional Information

 ls -l /var/run/docker.sock
lrwxr-xr-x  1 root  daemon  29 May  2 12:06 /var/run/docker.sock -> /Users/me/.rd/docker.sock

cat /Users/me/.rd/docker.sock
cat: /Users/me/.rd/docker.sock: No such file or directory

Rancher Desktop Version

1.3.0

Rancher Desktop K8s Version

1.22.7

Which container runtime are you using?

moby (docker cli)

What operating system are you using?

macOS

Operating System / Build Version

macOS Monterey

What CPU architecture are you using?

arm64 (Apple Silicon)

Linux only: what package format did you use to install Rancher Desktop?

No response

Windows User Only

No response

Issue Analytics

State:
Created a year ago
Comments:14 (4 by maintainers)

Top GitHub Comments

1reaction

janduboiscommented, May 7, 2022

@jandubois , maybe time to re-open the issue, since you have now multiple user reports?

I will re-open if people can confirm that they ran into this issue while having “administrative access” (sudo) enabled!

If you run without sudo access, then RD cannot update the symlink and you have to run

docker context use rancher-desktop

to tell docker to use the RD context to find the socket.

I know the dialogs are not really clear about this and have opened #2178 to improve this.

So if anybody experiences this issue while using “sudo” mode, please respond here, and I’ll re-open. I still don’t know what we can do about it, as there hasn’t been enough information to reproduce the problem, but let’s see what people report!

0reactions

janduboiscommented, May 31, 2022

It is not clear to me why 1.2.1 was still looking for ~/.rd though

It isn’t. I think 1.2.1 does not create a docker context at all; it relies on being able to create the symlink at /var/run/docker.sock and you need to switch back to the default context to use it.