rancher-desktop

rancher-desktop copied to clipboard

Actual Behavior

Steps to Reproduce

1. Install Rancher Desktop and it runs for a while, then quit by itself.
2. Click the icon in the Dock to relaunch

Result

Kubernetes Error Rancher Desktop 1.6.0 - darwin (x64) Error Starting Kubernetes Error: /Applications/Rancher Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl exited with code 1 Last command run: /Applications/Rancher Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl start --tty=false 0

Context: Starting virtual machine

Some recent logfile lines:

'time="2022-10-13T00:44:02+08:00" level=fatal msg="errors inspecting instance: [failed to get Info from \\"/Users/<user_name>/Library/Application Support/rancher-desktop/lima/0/ha.sock\\": Get \\"http://lima-hostagent/v1/info\\": context deadline exceeded]"\n',

code: 1, command: [ '/Applications/Rancher Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl', 'start', '--tty=false', '0' ] }

Expected Behavior

Start running.

Additional Information

No response

Rancher Desktop Version

Rancher Desktop 1.6.0 - darwin (x64)

Rancher Desktop K8s Version

1.24.6

Which container engine are you using?

containerd (nerdctl)

What operating system are you using?

macOS

Operating System / Build Version

macOS Monterey12.6

What CPU architecture are you using?

x64

Linux only: what package format did you use to install Rancher Desktop?

No response

Windows User Only

No response

Cannot even start again in the first few hours

Please attach full logs.

It's in the "Result" section above, which was shown in the popup

@jandubois are you referring to

I am experiencing the same error under pop!_os (ubuntu based) with the deb packaged version when I upgraded to 1.6.0. It's the same error message the the original poster but with Linux based system locations.

The specific error I see is...

Error starting lima: Error: /opt/rancher-desktop/resources/resources/linux/lima/bin/limactl exited with code 1
    at ChildProcess.<anonymous> (/opt/rancher-desktop/resources/app.asar/dist/app/background.js:1:7750)
    at ChildProcess.emit (node:events:390:28)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:290:12) {
  stdout: '',
  stderr: 'time="2022-10-12T13:42:55-04:00" level=info msg="Using the existing instance \\"0\\""\n' +
    'time="2022-10-12T13:42:55-04:00" level=fatal msg="errors inspecting instance: [failed to get Info from \\"/home/mfarina/.local/share/rancher-desktop/lima/0/ha.sock\\": Get \\"http://lima-hostagent/v1/info\\": dial unix /home/mfarina/.local/share/rancher-desktop/lima/0/ha.sock: connect: connection refused]"\n',
  code: 1,
  command: [
    '/opt/rancher-desktop/resources/resources/linux/lima/bin/limactl',
    'start',
    '--tty=false',
    '0'
  ]
}

Note, this instance was docker/moby WITHOUT a running Kubernetes.

On Intel Mac the upgrade had no issues. That setup was docker/moby without a running Kubernetes as well.

My log files can be downloaded from https://1drv.ms/u/s!At6-pjJ-bCdxoERe8pHm0RsPPIRS?e=hjaCn7

Starting it up again (there was a reboot in between) and it just started

Has anyone managed to find a workaround for this problem?

Has anyone managed to find a workaround for this problem?

We have not been able to reproduce it, and for Matt the issue was gone once he restarted his machine, so not really clear what can be done about it. Is it more persistent for you?

yes... my first attempt at a solution was to restart... I updated to Ventura 13.1 but I don't know if it was related. and kubernetes was always disabled. apparently this error happens on kubernets startup when rancher starts

I solved my problem by reinstalling rancher desktop

i solved my problem by enlarge memory allocate

I solved this issue by resetting Kubernetes in the Troubleshooting section:

I'm going to close this as not-reproducible. I don't see anything we can do unless we have a repro case.

I am facing same problem on Ubuntu, this is "random". Starting my machine and sometimes it happens - only way to work this around is to restart laptop. Restarting Rancher, or using reset Kubernates in Troubleshooting section did not help. Occurs maybe each second day. Which log file would be best to provide?

ok.. I followed mentioned above thread .. Factory reset fixed this issue (for now at least)

.. only for couple of restarts ... problem came back. Something seems not stable enough. Probably reset to Factory settings is good short term workaround to use.

I had this issue today after turning off and on my laptop. It seems that some files were not deleted after shutting down my Ubuntu OS.

Just deleting manually the *.sock and .pid files (qemu.pid, serialv.sock, ha.sock, ga.sock and similars ) from the ~/.local/share/rancher-desktop/lima/0 directory was enough.

I had this issue today after turning off and on my laptop. It seems that some files were not deleted after shutting down my Ubuntu OS.

Just deleting manually the *.sock and .pid files (qemu.pid, serialv.sock, ha.sock, ga.sock and similars ) from the ~/.local/share/rancher-desktop/lima/0 directory was enough.

Confirming that this fixed the issue for me as well (Ubuntu 22.04), thank you :raised_hands: