getting a new issue…

time="2022-11-24T02:48:12+05:30" level=info msg="The QEMU process seems already stopped"
time="2022-11-24T02:48:12+05:30" level=info msg="The host agent process seems already stopped"
time="2022-11-24T02:48:12+05:30" level=info msg="Removing *.pid *.sock under \"/Users/achanpur/.rdlima/0\""
time="2022-11-24T02:48:12+05:30" level=debug msg="Make sure \"rancher-desktop-bridged_bridge0\" network is stopped"
time="2022-11-24T02:48:12+05:30" level=debug msg="Make sure \"rancher-desktop-shared\" network is stopped"
time="2022-11-24T02:48:12+05:30" level=debug msg="Make sure \"host\" network is stopped"
time="2022-11-24T02:48:12+05:30" level=debug msg="Make sure \"rancher-desktop-bridged_en4\" network is stopped"
time="2022-11-24T02:48:12+05:30" level=debug msg="Make sure \"rancher-desktop-bridged_en5\" network is stopped"
time="2022-11-24T02:48:12+05:30" level=debug msg="Make sure \"rancher-desktop-bridged_en6\" network is stopped"
time="2022-11-24T02:48:12+05:30" level=debug msg="Make sure \"rancher-desktop-bridged_en7\" network is stopped"
time="2022-11-24T02:48:12+05:30" level=debug msg="Make sure \"rancher-desktop-bridged_en0\" network is stopped"
net.pid --vde-group=everyone --vmnet-mode=bridged --vmnet-interface=en0 /private/var/run/rancher-desktop-bridged_en0.ctl]"
time="2022-11-24T02:49:34+05:30" level=warning msg="Non-strict YAML is deprecated and will be unsupported in a future version of Lima" comment="main file \"/Users/achanpur/.rdlima/0/lima.yaml\"" error="[150:1] unknown field \"k3s\"\n      147 |     lima-rancher-desktop: lima-0\n      148 |     host.rancher-desktop.internal: host.lima.internal\n      149 |     host.docker.internal: host.lima.internal\n    > 150 | k3s:\n            ^\n      151 |   version: 1.25.4\n      152 | networks:\n      153 |   - lima: rancher-desktop-shared\n      154 |     "
time="2022-11-24T02:49:34+05:30" level=info msg="Attempting to download the image from \"/Applications/Rancher <http://Desktop.app/Contents/Resources/resources/darwin/alpine-lima-v0.2.16-rd-3.15.4.iso\%22%22|Desktop.app/Contents/Resources/resources/darwin/alpine-lima-v0.2.16-rd-3.15.4.iso\""> digest=
time="2022-11-24T02:49:34+05:30" level=fatal msg="failed to download the image, attempted 1 candidates, errors=[failed to download \"/Applications/Rancher <http://Desktop.app/Contents/Resources/resources/darwin/alpine-lima-v0.2.16-rd-3.15.4.iso\|Desktop.app/Contents/Resources/resources/darwin/alpine-lima-v0.2.16-rd-3.15.4.iso\>": failed to open source /Applications/Rancher <http://Desktop.app/Contents/Resources/resources/darwin/alpine-lima-v0.2.16-rd-3.15.4.iso|Desktop.app/Contents/Resources/resources/darwin/alpine-lima-v0.2.16-rd-3.15.4.iso>: open /Applications/Rancher <http://Desktop.app/Contents/Resources/resources/darwin/alpine-lima-v0.2.16-rd-3.15.4.iso|Desktop.app/Contents/Resources/resources/darwin/alpine-lima-v0.2.16-rd-3.15.4.iso>: no such file or directory]"
2022-11-23T21:19:34.182Z: + limactl --debug start --tty=false 0
2022-11-23T21:19:34.182Z: Error: /Applications/Rancher <http://Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl|Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl> exited with code 1
2022-11-23T21:19:34.184Z: Error starting lima: Error: /Applications/Rancher <http://Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl|Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl> exited with code 1
    at ChildProcess.<anonymous> (/Applications/Rancher <http://Desktop.app/Contents/Resources/app.asar/dist/app/background.js:17:141990|Desktop.app/Contents/Resources/app.asar/dist/app/background.js:17:141990>)
    at ChildProcess.emit (node:events:390:28)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:290:12) {
  command: [
    '/Applications/Rancher <http://Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl|Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl>',
    '--debug',
    'start',
    '--tty=false',
    '0'
  ]
}

That's odd. It looks like RD can't find the image that it runs as the VM. There might be an issue with your install, or maybe your environment. What happens if you do a factory reset and then run again? If that doesn't work, does it help to do a factory reset, and then reinstall?

Hi Adam thanks for your response, I was able to identify and fix this issue.. the problem was me trying to run the entire setup over my corporate VPN , somehow I thought its mandatory for me to set Rancher over my corporate vpn as i downloaded it from my company provided location.. but it was not the case.. hence was encountering all these weird issues that probably no one has come across…

Glad to hear your problem is resolved!