Avoid giving admin privileges after restart on MacOS #1814
-
Hi, after reading many issues and discussions in the repo, I start this new discussion seeking some help. I work with a personal MacBook Air (M1, 2020, MacOS BigSur 11.6.4) and use rancher desktop 1.1.1 as my container manager. We would like to extend its use to all corporate computers but we have a big caveat, after each restart this prompt asks for root permissions: The main problem is that workers with corporate Macs do not have admin credentials. Thanks in advance! |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 12 replies
-
The reason for the prompt is that macOS completely deletes the contents of We are getting rid of We have not yet implemented a way to create the docker socket in a user-owned location, so this will continue to prompt for sudo access unless you switch to containerd and nerdctl. See also #1820 for some work-in-progress. It mentions the need for a followup PR to move the docker socket location. Unfortunately it looks like these changes will not yet make it into the next release (which has become urgent due to the recent breakage with macOS Monterey 12.3, e.g. #1815). |
Beta Was this translation helpful? Give feedback.
-
@jandubois thanks for the thorough explanation! I was able to find the socket using ![]() Consequently I was able to disable administrative access permanently in the RD startup screen and use RD without the daily popup. |
Beta Was this translation helpful? Give feedback.
The reason for the prompt is that macOS completely deletes the contents of
/var/run
on each reboot.We are getting rid of
/var/run/rancher-desktoplima
in the next release for that reason. We are going to create the files directly inside the/var/run
directory (with arancher-desktop
prefix in the filename) to avoid having to recreate the directory.We have not yet implemented a way to create the docker socket in a user-owned location, so this will continue to prompt for sudo access unless you switch to containerd and nerdctl.
See also #1820 for some work-in-progress. It mentions the need for a followup PR to move the docker socket location. Unfortunately it looks like these changes will n…