This message was deleted.
# rancher-desktop
a
This message was deleted.
f
Eventually, I get
However, I can't turn off Kubernetes, which I don't need, since I can't open the settings dialog!
f
You can run
rdctl factory-reset
from the shell (but it will delete the VM and all your settings). Then you should get the first-run dialog again, and you can disable k8s. However, I'm not convinced your problem is related to running kubernetes
Does your computer run device management software, like JamF? If yes, could you check with your IT department if your device profile has just been changed?
We have seen a number of errors like this, and they seem to be related to something called
mcxalr
, but we have not been able to reproduce it ourselves. So if your profile has just changed, it would be useful to know what changes have been made.
f
Interesting. I don't think we use JamF, but I'll see what I can find out. Thanks! I'll try the nuclear option and let you know what happens.
Same issue after a reset and a clean install
f
It could be some other device management software;
mcxalr
is an (ancient) component that is part of the OS, that some profiles use to check if specific binaries are allowed to launch or not.
f
what binary would it be trying to launch?
I see this log now
Copy code
'--tty=false',
    '/Users/rwhitlock/Library/Application Support/rancher-desktop/lima/_config/0.yaml'
  ],
  stdout: '',
  stderr: 'time="2023-10-05T19:06:08-07:00" level=info msg="Terminal is not available, proceeding without opening an editor"\n' +
    'time="2023-10-05T19:06:08-07:00" level=fatal msg="instance \\"0\\" already exists (\\"/Users/rwhitlock/Library/Application Support/rancher-desktop/lima/0\\")"\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 /Users/rwhitlock/Library/Application Support/rancher-desktop/lima/_config/0.yaml'
}
f
Hmm, this is something different. I wonder if the factory-reset did kill all the processes.
f
Can I kill that directory?
"/Users/rwhitlock/Library/Application Support/rancher-desktop/lima/0
f
Maybe you can do another factory-reset, and then reboot the machine before starting Rancher Desktop again, to make sure there are no left-over processes from the previous instance
f
That's a good idea
f
Please use
rdctl factory-reset
instead. It will delete that directory, but also clean up various other places.
f
interesting
Copy code
factory-reset                                          rbenv:system 
ERRO[0000] Error trying to delete the Lima VM: exit status 1
f
After the reset and reboot, if you still see an error, please check the log file again and see if the error is an EACCES error running
limactl.ventura
. This is the bug I was talking about before. It is allowed to run a couple of times, but then suddenly is forbidden.
Maybe try the factory-reset after the reboot
f
Does RD have to be running for me to have access to
rdctl
?
f
Not sure that the
rbenv:system
is doing there though.
f
yeah that's been annoying me for a while, I can't get rid of it
f
No, rdctl is symlinked from
~/.rd/bin/rdctl
, and that directory will be in your
PATH
if you enabled automatic path management (should have been the default)
f
huh, I did. I get a command not found when I quit RD
f
idk, this will be something in your shell profile
f
yeah. Fair enough. I do see
:/Users/rwhitlock/.rd/bin
in my path tho
anyway... I'll try the reboots and get back to you
👍 1
thanks for the help, I appreciate it
So I rebooted, and reinstalled. It was already in a factory reset state. Same error, but when I tried to do the resest from the cli, I got this.
Copy code
[~]$ rdctl factory-reset 
ERRO[0000] Error trying to delete the Lima VM: exit status 1 
[~]$ rdctl factory-reset
zsh: command not found: rdctl
f
Oh, I think factory-reset will remove
~/.rd
😞
So this might be normal. Did you check the logs on the first failed run? Did you see the EACCES error or something else?
f
Where is that log file again? hsa.error?
f
Could you create a Github issue and upload the log files to it? I want to finish a code review. and then I have to take care of some personal stuff, so won't be able to look further tonight.
f
Sure, thanks again.
f
All the logs are in
~/Library/Logs/rancher-desktop
f
ah, thanks
f
Thanks!