This message was deleted.

Restart the terminal?

no luck

is your <user>/.rd/bin in your path?

yeah

so its in the path, but no binaries are there?

huh, I do see the binaries, maybe something funky is going on with my PATH even though the entry is there so if I use

~/.rd/bin/kubectl

it works, but not

kubectl

yeah that is a bit odd. and assuming

which kubectl

doesn’t work as well.

thanks guys

thought the installer added the ~/.rd/bin to path, but when dealing w sudo etc that can be hit or miss. i didn’t see a paths.d file for RD which can be a bit easier than the long delimited option

I use a non-standard shell (fish) so I opted out of the ‘set it for me’ option as I figured it would not configure fish properly. Turns out, neither can I 😆 It was a different variable basically instead of

PATH

I needed to add it to

fish_user_paths

RD is supposed to configure fish correctly. Does it not work? For me it writes

$ cat ~/.config/fish/config.fish
### MANAGED BY RANCHER DESKTOP START (DO NOT EDIT)
set --export --prepend PATH "/Users/jan/.rd/bin"
### MANAGED BY RANCHER DESKTOP END (DO NOT EDIT)

technically I did not try because during installation I selected the ‘do it myself’ option because I didn’t think fish would be supported

And that works for me:

$ fish
Welcome to fish, the friendly interactive shell
Type help for instructions on how to use fish
jan@mactop ~> which helm
/Users/jan/.rd/bin/helm
jan@mactop ~>

might try reinstalling to verify that no manual config was necessary

That's fine. Note that you can still enable it later via the Preferences dialog, but if you have it working now, then it is all good 🙂