https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# rancher-desktop
a
This message was deleted.
r
Can you please look into the log files and see if there are any error messages? You can open the folder containing logs via 
Troubleshooting > Show Logs
b
I fixed the issue by switching from QEMU to VZ
👍 1
r
We are fixing a bug related to Rancher Desktop with QEMU not working on macOS. If you want to switch back to QEMU you may want to try the upcoming 1.12 release with this fix.
f
This will not be fixed in 1.12. The only known fix right now would in turn break support on M1. This is still being worked on upstream and will be updated once it is fixed properly in QEMU itself. For the time being using VZ emulation is the only supported way on M3 CPUs.
👍 1
b
I have the same issue
on a macbook pro with m3pro chip After 5 minutes I get...
Copy code
'/bin/sh',
    '-c',
    'rm -f /usr/local/share/ca-certificates/rd-*.crt'
  ],
  stdout: '',
  stderr: '',
  code: 255,
  [Symbol(child-process.command)]: '/Applications/Rancher <http://Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl.ventura|Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl.ventura> shell --workdir=. 0 sudo /bin/sh -c rm -f /usr/local/share/ca-certificates/rd-*.crt'
}
f
I think this is a separate issue, but I would need to see a bit more context from the log file (what I'm looking for is if this is the dreaded 
EACCES
error).
I assume you are already using VZ emulation and not QEMU?
b
i have no clue what vz is
f
If you are not using VZ, then you should try to see if that fixes your problem because QEMU is known to be broken on M3 cpus. I thought it would have failed even earlier, but it is not completely deterministic.
b
i used qemu and switched to vz, now restarting
now i get an immediate error
Copy code
'--tty=false',
    '0'
  ],
  stdout: '',
  stderr: 'time="2023-12-11T22:07:35+01:00" level=info msg="Using the existing instance \\"0\\""\n' +
    'time="2023-12-11T22:07:35+01:00" level=fatal msg="errors inspecting instance: [host agent is running but driver is not]"\n',
  code: 1,
  [Symbol(child-process.command)]: '/Applications/Rancher <http://Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl.ventura|Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl.ventura> start --tty=false 0'
}
f
Can you try doing a factory reset?
Copy code
/Applications/Rancher\ <http://Desktop.app/Contents/Resources/resources/darwin/bin/rdctl|Desktop.app/Contents/Resources/resources/darwin/bin/rdctl> factory-reset
After quitting the app
b
i must admit i did a force quit cause i did not want to wait 5 min, maybe restarting helps, one moment
now everything looks fine
f
It looks like some background processes are still running, so they need to be removed properly
b
no errors
seems to work
f
Ok, good. I hope everything works for you now. Because we don't have a solution for the 
EACCES
issue; we can't even reproduce it locally. But it isn't specific to M3 machines, so hopefully you don't run into it.
That looks correct. Does 
kubectl get no
work?
b
thank you sooo much !!! Wish you a nice evening
f
You are welcome! Have a great evening yourself!
b
@brave-nest-1207 sorry for hijacking your thread, but it looked for me you had the same error, hope yours will be solved
f
It seems after all to be the same issue, so should be all good.
✅ 1
b
No worries, I switched to VZ and solved the issue for me, but hopefully QEMU will be fixed in the future.
f
Looks like a fix is scheduled for QEMU 8.2.1 at the end of January... And then we still have to update the bundled QEMU in Rancher Desktop, so maybe in a February release.
39 Views
Open in Slack
PreviousNext
Powered by