Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Improve user experience around symlinks for supporting utilities

See original GitHub issue

For bugs, describe what you’re seeing RD does not recognize the clients apps, such as nerdctl, kubectl, helm …

To Reproduce Steps to reproduce the behaviour:

Open RD
Navigate to Supporting Tools
Tools checkboxes not enabled.

Result Supporting tools not found (not linked).

Expected behaviour Should link supporting tools properly.

Screenshots Screen Shot 2021-11-01 at 10 08 24 AM

Setup (please complete the following information):

OS: macOS Monterey
Rancher Desktop version: 0.6.0
Kubernetes version: 1.21.5

Issue Analytics

State:
Created 2 years ago
Comments:7 (4 by maintainers)

Top GitHub Comments

6reactions

rkazakcommented, Nov 13, 2021

I too am having a similar issue. I have a fresh laptop with Big Sur installed. I used the ‘.dmg’ as my install source.

I see the following after starting up Rancher Desktop.

So to get around this I added my user account to the wheel group and changed the permissions on the /usr/local/bin directory to 775, giving group wheel write perms into that directory. This allowed the installation to complete successfully. Also I had other issues on reinstalls but that perms issue did not re-occur.

2reactions

ekloccommented, Nov 8, 2021

This is working as expected: The user has moved Rancher Desktop.app to $TMPDIR and ran it from there, creating the symlinks.

I run into similar issue on OSX Catalina. On OSX I did’t move the app to $TMPDIR. I run the app from Downloads folder (since I couldn’t move the app to Applications folder as I’m not a local admin) which created symlinks to @TMPDIR/T/AppTranslocation/209EA1E3-88D1-45C0-B4C9-0FE74CFA6F38/d/Rancher Desktop.app/Contents/Resources/resources/darwin/bin location.

Worked fine at first but after couple of days I noticed my kim and nerdctl would not work as my symlink was pointing to slightly different folder (@TMPDIR/T/AppTranslocation/220-EA1E3-xxx-…/d/Rancher Desktop.app/Contents/Resources/resources/darwin/bin). Not sure how it changed but I fixed the issue by deleting the symlink, restarting the RD app and checking the checkmark next to kim and nerdctl which created the symlink correctly.

Maybe it would make sense to auto delete old and re-create new symlink when an existing symlink points to a file that doesn’t exist?