rancher-desktop: Rancher Desktop fails to start on MacOS 12.3
Noticed Rancher Desktop (1.1.1) now fails to start after the MacOS update to 12.3
Steps to Reproduce
- Update MacOS to 12.3
- Open/Start Rancher Desktop
- Authorize privilege access
Result
Kubernetes Error
Error Starting Kubernetes
Error: /Applications/Rancher Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl exited with code 1
Last command Run:
limactl start --tty=false 0
Context:
Starting virtual machine
Some recent logfile lines:
time="2022-03-15T04:59:58-07:00" level=info msg="Using the existing instance \"0\""
time="2022-03-15T04:59:58-07:00" level=info msg="Starting switch daemon for \"shared\" network"
time="2022-03-15T04:59:58-07:00" level=fatal msg="\"/private/var/run/rancher-desktop-lima\" doesn't seem to be writable by the daemon (gid:1) group"
2022-03-15T11:59:58.940Z: + limactl start --tty=false 0
2022-03-15T11:59:58.940Z: Error: /Applications/Rancher Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl exited with code 1
2022-03-15T11:59:58.940Z: Error starting lima: Error: /Applications/Rancher Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl exited with code 1
at ChildProcess.<anonymous> (/Applications/Rancher Desktop.app/Contents/Resources/app.asar/dist/app/background.js:1:8692)
at ChildProcess.emit (node:events:394:28)
at Process.ChildProcess._handle.onexit (node:internal/child_process:290:12)
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 49
- Comments: 30 (8 by maintainers)
We have determined the root cause of this issue:
Rancher Desktop has always erroneously created
/private/var/run/rancher-desktop-limawith file mode555.We didn’t notice this because it was silently fixed by lima when it made sure the directory existed:
Now, this is actually a bug:
mkdir -m 755 -p ...is not supposed to change the permission bits if the directory already existed. But it did, so it covered up the bug in Rancher Desktop.This bug has been fixed in the Monterey 12.3 release (but not in e.g. the Catalina security update).
The best workaround for now is to run this command after each reboot (
/var/runis deleted on reboot), before you invoke Rancher Desktop the first time:We are planning to make a new Rancher Desktop release next week that addresses this issue.
The permissions on the
/private/var/run/rancher-desktop-limadirectory were reset to555.Workaround is resetting it to
775.yes, i just updated and i’m facing the same issue
I installed rancher desktop today on my intel macbook pro 2019 with montery 12.3 and faced the same issue. in my case the directory was already present but with the wrong permissions i had to run:
sudo chmod 775 /private/var/run/rancher-desktop-limainstead.Getting error in mac monterey 12.5 after launching rancher desktop. Sharing the 2 screenshots for the reference
I tried some suggested solutions but not working
@mariusrugan Note that I said “current CI build”. It cannot be fixed for the code already released, but will be fixed in the next release (later this week).
You can test the current 1.2 release candidate by downloading from https://github.com/rancher-sandbox/rancher-desktop/actions/runs/2007360261. Note that these builds are not signed, so you’ll have to remove the quarantine attributes after installation.
Looks like the permissions applied to wrong directory, try again - should look like this instead:
With #1758 we should no longer use that directory (just
/private/var/rundirectly), so that should no longer be an issue in the next release (but it hasn’t shipped yet).Note that it’s checking the directory is group-writable, so
0755wouldn’t work; you’d need0775or something along those lines.To me it doesn’t start even with 775 permissions:
Error is same:
Tried reinstalling rancher desktop both via brew and manually but it still fails with same error
Have you tried these?

@AdnanHodzic Your issue is a duplicate of #1615 and not of this one.
This issue:
"/private/var/run/rancher-desktop-lima" doesn't seem to be writable by the daemon (gid:1) groupYour error:
sudo: a password is required.Running either
sudo mkdir -m 775 /private/var/run/rancher-desktop-limaand/orsudo chmod 775 /private/var/run/rancher-desktop-limadoes not fix the issue for me on MacOS 12.3 (Intel).@alexdepalex Thanks that works.