https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# rancher-desktop
a
This message was deleted.
w
how did you install RD? almost sounds like an install as a different user than the one you are running as so the perms are off
w
thats exactly what happened! I restrict brew to my admin user thats used to set up these machines. So Rancher Desktop is running on a standard users account
w
ahh yeah that could get a bit messy since the ownership of the folder is wrong.
w
what folders would the user need to own?
w
its going to need access to the App so make sure that looks clean
w
I am checking now
w
brew also really doesn’t like running as a different user
thats why it will toss an error if you try and install as root
and are you rolling 1.3 or 1.2?
w
@polite-mouse-38756 FYSA
we are running 1.3 right now
👍 1
w
i thought 1.3 was getting away from using /usr/local/bin so you don’t have to chown it, but could be misremembering
w
regarding this command 
ls -la /Applications/Rancher\ <http://Desktop.app/Contents/Resources/resources/darwin/lima/bin|Desktop.app/Contents/Resources/resources/darwin/lima/bin>
everything seems to be owned by my logged in user
w
cool how about /usr/local/bin?
w
/usr/local/bin
is all owned by root
w
you are on an M1 so the homebrew bits should be in /opt so chowning /usr/local/bin shouldn’t be too disruptive
w
so would each standard user need to own 
/usr/local/bin
??
w
it needs to be writable based on that err. there can only be one owner
trying to track down where the RD folks were shifting away from usr/local/bin to a dedicated folder
w
understood on that, I don’t need my admin to own it. I will say, giving my standard user ownership over 
/usr/local/bin
doesn’t seem to have changed anything 😢
w
so you still have a write permission issue for RD after giving the user ownership over /usr/local/bin?
w
I noticed that when searching through your issues. Yeah, attaching a screenshot here
w
so did you own the contents of bin or the directory itself?
w
I own all of the children of 
/usr/local/bin
and of the directory 
/usr/local/bin
w
so rancher is running as sheldon.mcclung and sheldon.mcclung can’t write to that path even though they own it. thats a head scratcher to me 🤔. may need the real Rancher team to step in
i think you are in a similar situation as https://github.com/rancher-sandbox/rancher-desktop/issues/1560
w
Sorry I had to step away from this for a bit with customer demands. I will look into that issue. In the meantime, please let me know how I can assist in troubleshooting. I haven’t been able to find any good path forward towards getting this to work consistently.
so regardless, given that I have a fully automated workstation setup, Rancher Desktop is going to be installed by either root or root su’ing into an admin user. Either way I think I might run into the problem stated above
4 Views
Open in Slack
PreviousNext
Powered by