Error Starting Kubernetes [Mac OS Monterey v12 beta]

[drdoug007]

Hi, I am getting "Error Staring Kubernetes" when starting Rancher Desktop on my Mac Laptop. It looks likes I am missing libglib.

Desktop.app/Contents/Resources/resources/darwin/lima/Cellar/qemu/6.0.0/bin/../opt/glib/lib/libglib-2.0.0.dylib' (no such file), '/usr/lib/libglib-2.0.0.dylib' (no such file)

Process:               qemu-img [31504]
Path:                  /Applications/Rancher Desktop.app/Contents/Resources/resources/darwin/lima/Cellar/qemu/6.0.0/bin/qemu-img
Identifier:            qemu-img
Version:               0
Code Type:             X86-64 (Native)
Parent Process:        ??? [31501]
Responsible:           Rancher Desktop [31463]
User ID:               501

Date/Time:             2021-08-19 07:08:19.831 +0700
OS Version:            macOS 12.0 (21A5304g)
Report Version:        209
Bridge OS Version:     3.0 (14Y908)
Anonymous UUID:        5B26757E-ABA5-1AD7-E97D-F209EFD56DF8

Sleep/Wake UUID:       CE10A92A-FD03-40DD-8685-9E2F76150B8E

Time Awake Since Boot: 130000 seconds
Time Since Wake:       13000 seconds

System Integrity Protection: enabled

Crashed Thread:        0

Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Termination Reason:    DYLD, [0x1] Library missing

Application Specific Information:
Library not loaded: @executable_path/../opt/glib/lib/libglib-2.0.0.dylib
  Referenced from: /Applications/Rancher Desktop.app/Contents/Resources/resources/darwin/lima/Cellar/qemu/6.0.0/bin/qemu-img
  Reason: tried: '/Applications/Rancher Desktop.app/Contents/Resources/resources/darwin/lima/Cellar/qemu/6.0.0/bin/../opt/glib/lib/libglib-2.0.0.dylib' (no such file), '/usr/lib/libglib-2.0.0.dylib' (no such file)

Dyld Error Message:
  Library not loaded: @executable_path/../opt/glib/lib/libglib-2.0.0.dylib
  Referenced from: /Applications/Rancher Desktop.app/Contents/Resources/resources/darwin/lima/Cellar/qemu/6.0.0/bin/qemu-img
  Reason: tried: '/Applications/Rancher Desktop.app/Contents/Resources/resources/darwin/lima/Cellar/qemu/6.0.0/bin/../opt/glib/lib/libglib-2.0.0.dylib' (no such file), '/usr/lib/libglib-2.0.0.dylib' (no such file)

Binary Images:
       0x10fd1d000 -        0x10fe48fff +qemu-img (0) <7C5C890C-8482-3FE3-87A2-4D2DEEE67065> /Applications/Rancher Desktop.app/Contents/Resources/resources/darwin/lima/Cellar/qemu/6.0.0/bin/qemu-img
       0x11d9c7000 -        0x11da2efff  dyld (931) <E604D5FB-9CEC-336F-945B-CBDA1A199E67> /usr/lib/dyld

[jandubois]

Thank you for your bug report!

I've confirmed the issue on Monterey Public Beta.

The issue is that the dynamic loader seems to have changed the way @executable_path is resolved when the executable is a symlink. In Catalina and Bigsur it refers to the location of the symlink itself, whereas in Monterey is seems to refer to the location of the resolved symlink (the target).

[jandubois]

I could get Rancher Desktop 0.4.1 working on Monterey Beta with the following hack:

cd /Applications/Rancher\ Desktop.app/Contents/Resources/resources/darwin/lima/bin
rm qemu*
mv ../Cellar/qemu/6.0.0/bin/qemu-img .
mv ../Cellar/qemu/6.0.0/bin/qemu-system-x86_64 .

Stop and restart Rancher Desktop and it will display an error from the GUI (I'll file a separate bug for that; clicking "Ok" allows you to proceed) and kubernetes will be installed.

There is yet another issue that Monterey doesn't have a /usr/local/bin directory, so the logic to create a symlink for helm, kim, or kubectl will fail unless you create the directory first:

sudo mkdir /usr/local/bin
sudo chown $USER /usr/local/bin

The error dialog appear on each restart of Rancher Desktop, but otherwise it appears to be functional.

If you feel adventurous, please follow these workarounds and report if you run into any other issues on Monterey Beta!

[drdoug007]

The workaround is working for me :)
Thanks

[jandubois]

The workaround is working for me :)

Awesome! Could you please confirm if you also get the error dialog from #519!

[drdoug007]

No I did not get any error dialog, and there was no errors in the console.

[pulberg]

Same error on macOS BigSur 11.5.2

[jandubois]

Same error on macOS BigSur 11.5.2

@pulberg Can you attach some log that shows the same error?

I've just tested Rancher Desktop 0.4.1 on both macOS 11.3 and 11.5.2, and it worked as expected in both cases.

[jandubois]

it worked as expected in both cases

Actually, it didn't; the kim image manager was not installed correctly, but that is a different issue than the original poster had.