https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# rancher-desktop
a
This message was deleted.
f
Have you been using Rancher Desktop before, and it just start throwing this error? Maybe you ran out of space inside the VM by creating/pulling lots of images and never pruning out the ones no longer used?
If (and only if) this is your problem, you can try to increase the size of the volume a bit, to allow Rancher Desktop to start again, but then you must remove old/unused images, or you will run into the same issue again soon:
Copy code
/Applications/Rancher\ <http://Desktop.app/Contents/Resources/resources/darwin/lima/bin/qemu-img|Desktop.app/Contents/Resources/resources/darwin/lima/bin/qemu-img> resize "$HOME/Library/Application Support/rancher-desktop/lima/0/diffdisk" +10G
This is a single command you have to run from the terminal.
Alternatively, if you don't care about preserving your existing images, you can do a factory reset from the commandline:
Copy code
rdctl factory-reset
It will remove the existing volume and all your settings
b
Resizing the images allows Rancher Desktop to start
Copy code
2023-05-11T16:22:26.904Z: CLI server is now ready.
2023-05-11T16:22:26.913Z: Credentials server is now ready.
But the docker daemon was not started. I did an update today. In previous version, starting rancher desktop automatically starts docker (I disabled kubernetes).
Copy code
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
f
Check the docker log to see if there are any errors:
Copy code
rdctl shell cat /var/log/docker.log
b
Copy code
cat: can't open '/var/log/docker.log': No such file or directory
f
Are you using 
moby
or 
containerd
?
b
containerd
f
Ok, then the docker socket doesn't exist and the daemon isn't running. Where do you get the error message about not being able to connect to docker?
b
I just ran a 
docker ps
on the terminal. In previous version of rancher desktop, it works
f
That doesn't sound correct; you would have to run 
nerdctl ps
if you are using 
containerd
b
my bad, I was probably using moby
f
Ok, assuming things work for you again, please make sure you do 
docker image prune
or similar to reclaim some space inside the VM volume
You can check the available space on the data volume with
Copy code
$ rdctl shell df -h /mnt/data
Filesystem                Size      Used Available Use% Mounted on
/dev/disk/by-label/data-volume
                         97.9G      2.1G     90.7G   2% /mnt/data
b
Thanks! Yes, I did the system prune all but didn't reclaim any space. I will have to look at my images/containers
290 Views
Open in Slack
PreviousNext
Powered by