limactl doesn't exist on M1 chip mac

[mmhealey1]

Actual Behavior

File /Applications/Rancher Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl doesn't exist.

Steps to Reproduce

Run Rancher Desktop

Result

2022-08-22T11:04:51.725Z: Error starting lima: se [Fatal Error]: File /Applications/Rancher Desktop.app/Contents/Resources/resources/darwin/lima/bin/limactl doesn't exist.
    at Ur.ensureArchitectureMatch (/Applications/Rancher Desktop.app/Contents/Resources/app.asar/dist/app/background.js:17:206482)
    at async /Applications/Rancher Desktop.app/Contents/Resources/app.asar/dist/app/background.js:17:228437 {
  fatal: true
}

Expected Behavior

Should boot up and work

Additional Information

No response

Rancher Desktop Version

1.5.1

Rancher Desktop K8s Version

1.24.3

Which container engine are you using?

moby (docker cli)

What operating system are you using?

macOS

Operating System / Build Version

macOS Monterey 12.5.1

What CPU architecture are you using?

arm64 (Apple Silicon)

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

No response

Windows User Only

No response

[mmhealey1]

This could be due to XProtectPayloads being updated on macOS today

[adamkpickering]

Thanks for the bug report! Have you tried running limactl by itself? I am curious if that will work.

Also, could you please post more logs here? Please enable debug mode in the Troubleshooting tab before reproducing the issue. Then you can access the logs via the Troubleshooting tab as well. Thanks!

[mmhealey1]

The issue is definitely with limactl. I tried installing it via homebrew independent of Rancher-Desktop and the same issue occurred. It looks like Apple security update deletes limactl because it thinks its malware.

On Mon, 22 Aug 2022, 23:05 Adam Pickering, @.***> wrote:

Thanks for the bug report! Have you tried running limactl by itself? I am curious if that will work.

Also, could you please post more logs here? Please enable debug mode in the Troubleshooting tab before reproducing the issue. Then you can access the logs via the Troubleshooting tab as well. Thanks!

— Reply to this email directly, view it on GitHub https://github.com/rancher-sandbox/rancher-desktop/issues/2798#issuecomment-1223188790, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMQGKBGMPNJCLMWVL4SMSKTV2P2RTANCNFSM57HHLD5Q . You are receiving this because you authored the thread.Message ID: @.***>

[AkihiroSuda]

The issue is definitely with limactl.

Isn't this an issue of macOS? Could you send the report to Apple?

[mmhealey1]

Yeah, already sent report to apple :)

On Wed, 24 Aug 2022, 04:11 Akihiro Suda, @.***> wrote:

The issue is definitely with limactl.

Isn't this an issue of macOS? Could you send the report to Apple?

— Reply to this email directly, view it on GitHub https://github.com/rancher-sandbox/rancher-desktop/issues/2798#issuecomment-1225129206, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMQGKBCTUBKRCD3CXJ7GT53V2WHHRANCNFSM57HHLD5Q . You are receiving this because you authored the thread.Message ID: @.***>

[przemekpln92]

Hi guys, a solution that worked for me and my teammates:

1. Remove rancher from your Applications
2. brew install --cask rancher
3. Go to Rancher --> Preferences a.In Application section Check Administrative Access b. In Container runtime switch to dockerd(moby)

MacOS Monetery 12.5.1 - Intel chip

[jandubois]

I understand this issue has been fixed by updating the AV definitions: https://github.com/lima-vm/lima/issues/1028