This message was deleted.
# rancher-desktop
a
This message was deleted.
k
Can you
rdctl shell
into the VM?
c
yes
k
Can you run
docker images
in the VM?
c
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
k
What does
ps auxww | grep docker
say?
c
it only returns
grep docker
k
And is there anything in
/var/log/docker.log
?
c
No such file or directory
k
Weird, it's like it didn't even bother trying to launch docker.
c
Docker was running
k
I think we'll need the logs. Could you file a bug at https://github.com/rancher-sandbox/rancher-desktop/issues and attach a zip of the logs?
c
It just stopped at some point. Same with kubernetes. But rancher desktop reports that it's running
which logs specifically? it is a work computer so I'll have to verify that I have permission to do so and nothing is sensitive
k
Yup. I want to see if the logs show when, and hopefully why, docker crashed. But it sounds like
supervise-daemon k3s
has also crashed
c
all of the logs from the folder?
k
Actually just the
lima*
and
k3s.log
ones
👍 1
And watch out for the symlinks, like
lima.ha.stdout.log
👍 1
c
Ok, I will check with work and file a bug with a zip of the logs. Thanks for helping confirm the issue reaching out to offer support
k
Or you could go through those files and look for a stacktrace, error message, or other suspicious activity, and report back.
c
The main thing I'm seeing is
Copy code
{
  "error": "stat /Users/andrewturnblad/Library/Application Support/rancher-desktop/lima/0/ga.sock: no such file or directory",
  "level": "warning",
  "msg": "connection to the guest agent was closed unexpectedly",
  "time": "2023-12-13T17:22:23-06:00"
}
in
ha.stderr.log
from the lima logs
there is a stack dump in
serial.log
k
Ah, we know about the guest-agent problem
c
Yep, I also had kubernetes not be able to start on a fresh install and had to switch to VZ emulation
This error is occurring after switching to VZ and fully restarting rancher desktop
I am using dockerd (but did not switch from containerd)
Still working on approval about submitting an issue/logs but reverting back to rancher desktop 1.10 worked as 1.10 does not exhibit the issue I am seeing with 1.11