question-mark
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.

docker socket not available after sleep/wake

See original GitHub issue

⚠️ Workaround for this issue ⚠️

If your docker socket (or file mounts) are broken in this way, please quit “Rancher Desktop” and start it again.


Rancher Desktop Version

1.0.0-beta1

Rancher Desktop K8s Version

1.22.5

What operating system are you using?

macOS

Operating System / Build Version

12.1

What CPU architecture are you using?

arm64 (Apple Silicon)

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

N/A

Windows User Only

No response

Actual Behavior

Client docker on macOS loses the sock connection with the docker agent on Lima VM. It happens after sleep wake process

macOS terminal

:~/ $ docker info                                                                                                                                                                                                               [9:27:08]
Client:
 Context:    default
 Debug Mode: false

Server:
ERROR: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
errors pretty printing info

when I connect to the lima VM and run docker info:

docker info
Client:
 Context:    default
 Debug Mode: false

Server:
 Containers: 11
  Running: 0
  Paused: 0
  Stopped: 11
 Images: 77
 Server Version: 20.10.11
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 1
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 1e5ef943eb76627a6d3b6de8cd1ef6537f393a71
 runc version: b9ee9c6314599f1b4a7f497e1f1f856fe433d3b7
 init version:
 Security Options:
  seccomp
   Profile: default
 Kernel Version: 5.10.88-0-virt
 Operating System: Alpine Linux v3.14
 OSType: linux
 Architecture: aarch64
 CPUs: 4
 Total Memory: 5.79GiB
 Name: lima-rancher-desktop
 ID: NRV2:C6GL:E4XF:CK4L:HIZZ:6EM4:3ERM:CCWW:DHGH:7F7F:CTIJ:WUMC
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

Steps to Reproduce

  1. Select the dockerd engine option
  2. Put the macOS on sleep mode for more than 1~ hour
  3. Turn it on again and run any docker related command on macOS

Result

/ $ docker info                                                                                                                                                                                                               [9:27:08]
Client:
 Context:    default
 Debug Mode: false

Server:
ERROR: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
errors pretty printing info

Expected Behavior

After awake daemon should be reachable via socket

Additional Information

I need directions regarding which information would be helpful for troubleshooting this. Same behavior foud in the issue #1119

Issue Analytics

  • State:open
  • Created 2 years ago
  • Reactions:53
  • Comments:64 (5 by maintainers)

github_iconTop GitHub Comments

21reactions
huukhanhcommented, Jun 20, 2022

I tried to make a symbolic link to file docker.sock in ~$USER/.rd/docker.sock and its work fine. Try this:

sudo ln -s ~$USER/.rd/docker.sock /var/run/docker.sock
16reactions
janduboiscommented, Feb 28, 2022

Would be better to report this issue on the lima repository?

It is fine here. I already started looking into it, and even reproduced the error once (after 3 days) on my M1 mini, but unfortunately had to reboot it to finish some work for the upcoming release, which is almost done now.

It will be my top priority to look into this problem once 1.1.0 has shipped.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Docker socket is not found while using Intellij IDEA and ...
As a workaround that will allow IntelliJ to connect to Docker you can use the TCP Socket checkbox and put in the Engine...
Read more >
Docker Engine post-installation steps
When the Docker daemon starts, it creates a Unix socket accessible by members of the docker group. On some Linux distributions, the system...
Read more >
dockerd - Docker Documentation
MOBY_DISABLE_PIGZ Do not use unpigz to decompress layers in parallel when ... If the specified socket activated files aren't found, then Docker will...
Read more >
Change Docker Desktop settings on Windows
Select to automatically start Docker Desktop when you log into your machine. ... The Network tab is not available in the Windows container...
Read more >
Use the Docker socket from the extension backend
In order to do so, you can use /var/run/docker.sock.raw . Docker Desktop mounts the socket that lives in the Desktop VM, and not...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found