This message was deleted.

I suspect you are either not using

moby

but running with

containerd

as the container engine, or you are not using "Administrative Access", so the socket is not in the default location. In that case you can run

docker context use rancher-desktop

.

I’m running into this issue as well on an M3. On 1.16.0. Was working fine then suddenly all my containers ran out of space. Relaunching didn’t work, restarting rancher caused this problem to show up

When you say your containers run out of space, is that disk space or memory? Have you tried increasing the memory size for the VM?

the memory issue wasn't clear to me -- I thought literally the database containers themselves were writing log files and filling up whatever space they were allocated. can't troubleshoot now though because the docker daemon won't launch

Is the virtual disk full?

$ ls -lh ~/Library/Application\ Support/rancher-desktop/lima/0/diffdisk
-rw-r--r--  1 jan  staff   9.0G  2 Oct 14:40 /Users/jan/Library/Application Support/rancher-desktop/lima/0/diffdisk

Yeah, the file is limited to 100GB, so may be at capacity. You can grow it a little bit manually, so the docker daemon can work again, and make sure you prune the filesystem of abandoned images and build system cache

ok, do I need to set a variable somewhere to expand that allowed file size?

I'm just testing it myself before giving you the commands 🙂 You MUST make sure Rancher Desktop is not running before you do this

just the command itself

501 18140  1694   0  5:45PM ttys000    0:00.00 grep --color=auto --exclude-dir=.bzr --exclude-dir=CVS --exclude-dir=.git --exclude-dir=.hg --exclude-dir=.svn --exclude-dir=.idea --exclude-dir=.tox qemu

This will increase the size of the disk by 10GB

seems happy

🪦 all the images

It should only remove dangling (unreferenced) images, unless you added the

-a

option, which will delete all images not currently in use for running containers

I did just for good measure, nothing critical on this thing

I hope this returned a healthy chunk of disk space to you. In the future you should do the pruning more frequently before you run out of space

😅 clearly my cronjob has failed to run

There is also a "Disk Usage" extension in the GUI that you can use to check on disk space

thank you so much!

It says "Docker Desktop" because the extension is from Docker Inc, but it works fine on Rancher Desktop too 😉

I'm seeing the same error message but instead when i run ls -lh ~/Library/Application\ Support/rancher-desktop/lima/0/diffdisk the 0 directory does not exist. I've also redownloaded and factory reset the latest version 1.16.0 several times.

I finally got it to work. Here is what I did, so hopefully it will help someone else. MacBook Pro comes with an M3 chip. M3 chipp is not supported until Rancher version 13. I could not use the latest version 1.16 because it breaks my app because a dependency using Coldbox (Ortus Solutions) that is not compatible with the latest version. I end up installing Rancher Desktop Version: 1.13.1 Network status: online Kubernetes: 1.30.5 CE: moby Somehow it seems like after you remove and reinstall the Rancher desktop, it keeps some info lingering there, so right after the reinstall, I did a reset to factory settings, and then it took the new version of Rancher desktop and worked properly. finally, when building the container, I had to reference the platform specifically for M3 chip otherwise it would not built. something like this:

docker build --build-arg COREENV=local --platform linux/amd64 -t $containerName:$tagName .

Thanks for your input everyone!

Unfortunately this did not work for me. I am on a non M3 Mac OS version Ventura 13.2.1