This message was deleted.
# rancher-desktop
a
This message was deleted.
f
QEMU is currently incompatible with M3 chips; this will be fixed upstream at the end of the month and should become available in Rancher Desktop in a February/March release. For the mean time you need to run in VZ emulation mode: Emulation (macOS) | Rancher Desktop Docs
t
I'll give that a try, thanks.
f
If you want to run Intel containers, then you may also want to enable Rosetta support. If you don't need it, don't enable it, as it will slow down the VM slightly.
t
Still having similar issues with VZ. Suppose I'll just wait for some updates and try again. Thanks for the info.
Copy code
'time="2024-01-02T22:10:09-08:00" level=info msg="[hostagent] Waiting for the essential requirement 1 of 5: \\"ssh\\""\n' +
    'time="2024-01-02T22:11:34-08:00" level=info msg="[hostagent] Waiting for the essential requirement 1 of 5: \\"ssh\\""\n' +
    'time="2024-01-02T22:13:00-08:00" level=info msg="[hostagent] Waiting for the essential requirement 1 of 5: \\"ssh\\""\n' +
    'time="2024-01-02T22:14:25-08:00" level=info msg="[hostagent] Waiting for the essential requirement 1 of 5: \\"ssh\\""\n' +
    'time="2024-01-02T22:15:51-08:00" level=info msg="[hostagent] Waiting for the essential requirement 1 of 5: \\"ssh\\""\n' +
    'time="2024-01-02T22:15:52-08:00" level=fatal msg="did not receive an event with the \\"running\\" status"\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/miller/Library/Application Support/rancher-desktop/lima/_config/0.yaml'
}
f
That would be a different issue, so maybe not fixed by an update. I would try to run the following commands from a shell:
Copy code
rdctl factory-reset
rdctl start --experimental.virtual-machine.type vz
If this still fails, then you should share some complete log files to see what else might be wrong (but I won't be able to look at it anymore tonight). Hopefully the factory-reset will fix things up though.
You may need to use the full path to
rdctl
, at least for the second command, because the factory reset will remove the symlink from the
PATH
. The location is at
Copy code
/Applications/Rancher\ <http://Desktop.app/Contents/Resources/resources/darwin/bin/rdctl|Desktop.app/Contents/Resources/resources/darwin/bin/rdctl>
(note that there is a space in the full path, you need to backslash-escape it, or put the full path in quotes)
t
Thanks for the time, I'll see how far that gets me and upload logs if I hit more problems. Much appreciated.
Seems to have done the trick! 🎉
🎆 2
It does beg the question though... why did a rdctl reset work when doing so via the interface didn't?
f
It does, but it is too late to figure out now. I suspect that there were processes not properly terminated, which prevented it from properly restarting. The factory-reset is killing all these processes with prejudice...
t
Odd. I'd had some similar issues with RD when isntalled via brew, and then installed from the dmg off the website. I'd attempted factory resets on both after getting errors, and not until I rand the reset and VM creation via cli did it seem to work... in either case, I thank you.
m
These commands are saviour of people who are using Apple M3 Processors .. Thank you @fast-garage-66093 🙌
Copy code
rdctl factory-reset
rdctl start --experimental.virtual-machine.type vz