https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# rancher-desktop
a
This message was deleted.
f
Can you press "Re-run" in the diagnostics? If that doesn't fix it, can you enable debug logging (on the Troubleshooting page), Re-run diagnostics once more, and then share the 
diagnostics.log
file?
s
Did that, didn't fix, here's the file...
f
Thanks. It looks like the logging for the RDBIN diagnostics didn't make it into the release 😞
Let me figure out a way to check this manually
s
Thank you 🙂
f
Can you run this from your shell: 
PATH=/usr/bin:/bin:/usr/sbin:/sbin bash -l -c 'echo $PATH'
s
Copy code
$ PATH=/usr/bin:/bin:/usr/sbin:/sbin bash -l -c 'echo $PATH'
/home/mdsh/.local/bin:/home/mdsh/bin:/usr/bin:/bin:/usr/sbin:/sbin:/snap/bin
f
Ok, so it does not have 
~/.rd/bin
in it. But if you open a new terminal window to create a new shell, it does?
s
Yes.
That being a new shell
f
I'm sorry, I'm confusing myself again by thinking this is macOS, which handles login shells differently. What does your 
~/.bash_profile
look like; does it have the 
PATH
logic too?
s
I have a 
~/.profile
(where I manipulate $PATH), and a 
~/.bashrc
(where RD put the $PATH manipulation code) but no 
~/.bash_profile
~/.profile
sources 
~/.bashrc
when a BASH env var exists
f
We add it to both, but maybe don't create 
~/.bashrc
if it doesn't exist. The problem is that 
.bashrc
is not read by a login shell, and the diagnostic always runs as a login shell.
s
Copy code
### MANAGED BY RANCHER DESKTOP START (DO NOT EDIT)
export PATH="/home/mdsh/.rd/bin:$PATH"
### MANAGED BY RANCHER DESKTOP END (DO NOT EDIT)
That ONLY exists in 
~/.bashrc
which was created by Ubuntu many years ago when this machine was first installed.
f
On macOS all terminal apps create shells as login shells (because they are started by launchd, so don't inherit any login environment otherwise), and I guess our tests on Linux always had a 
~/.bash_profile
as well
Just as a test, could you 
touch ~/.bash_profile
and re-run the diagnostics? You can delete it again afterwards
s
Done that...
f
Oops, sorry, forgot one step: Go to Preferences, switch 
PATH
management to "Manual", click "Apply", and then switch it back to "Automatic" (or just restart RD). Then re-run diagnostics and let me know if this one now passes
🙌 1
s
Yep - now RD has added the 
MANAGED BY RANCHER DESKTOP
stanza to 
~/.bash_profile
and the tests pass. But then 
~/.bashrc
is not sourced, so I'd want to copy the contents of 
~/.profile
into 
~/.bash_profile
in order to source various files... Shells are hard 😉
f
Yes, we need to think through this once more; can you file an issue with the details (important ones are that you don't have a 
.bash_profile
and that you are on Linux)?
s
Yep - I'll have to be no sooner than tomorrow, as I have to go now to drive 180 miles. Thanks 🙂
f
No worries, I can file one for you
s
f
Thanks you! Yes, I promised to create it for you, but then actually didn't 😞
👍 2
😀 1
2186 Views
Open in Slack
PreviousNext
Powered by