Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kubernetes Starting Error on MacOS #400

Closed
kasunsjc opened this issue Jul 2, 2021 · 10 comments
Closed

Kubernetes Starting Error on MacOS #400

kasunsjc opened this issue Jul 2, 2021 · 10 comments
Labels
kind/bug Something isn't working platform/macos

Comments

@kasunsjc
Copy link

kasunsjc commented Jul 2, 2021

Hi Getting the following error when starting Rancher Desktop

image

OS - macOS Big Sur
MacBook Pro Intel

@jandubois
Copy link
Member

When you start Rancher Desktop the first time on macOS, it asks for permission to change the file ownership (and setuid bit) of the hyperkit driver. The error message sounds like you didn't grant that permission. Rancher Desktop cannot work without this.

@jandubois jandubois added kind/bug Something isn't working platform/macos labels Jul 3, 2021
@kasunsjc
Copy link
Author

kasunsjc commented Jul 3, 2021

I didn't get any popup window to grant permissions. Let me know how can I give permission

@jandubois
Copy link
Member

Please delete Rancher Desktop from your /Applications folder and install it again. The first time you run it, you should get a dialog like this:

Screen Shot 2021-07-05 at 10 28 47 AM

Do you not get that?

@kasunsjc
Copy link
Author

kasunsjc commented Jul 5, 2021

Nope, I tried now. after I dragged the app to the application folder then run the app. Prompt the error starting Kubernetes permission error as above.

Didn't get the popup window to enter password.

@jandubois
Copy link
Member

@kasunsjc Are you running device management software or something similar that might prevent you from elevating privileges to administrator?

I've tested on Catalina and Big Sur, and created both Standard and Admin users, and I always get the prompt. When I cancel the prompt, I get the same error dialog, but that is expected, and exactly what the error says: "User did not grant permission".

@mook-as Any ideas under which conditions the dialog might not be displayed (or auto-cancelled)?

@mook-as
Copy link
Contributor

mook-as commented Jul 5, 2021

Hmm, we're doing a very boring invocation of sudo-prompt; it's possible that it's seeing some other error and thinking it's because the user didn't grant permission instead…

@jandubois
Copy link
Member

it's possible that it's seeing some other error and thinking it's because the user didn't grant permission instead…

I don't see how that would happen; shouldn't that still display the dialog?

@kasunsjc Normally I would suggest to add additional logging around this call to investigate what is going wrong. But the whole dialog will disappear in the next release because we will no longer need to change ownership/permissions, so digging much deeper is of limited use: there will be no way to ship any fix we might come up with.

So if this is fine with you, I would like to suggest to simply wait for the next release, which doesn't have a firm timeline, but hopefully should be out by the end of the month.

@kasunsjc
Copy link
Author

kasunsjc commented Jul 6, 2021

No rush. will wait till next release :)

@rkazak
Copy link

rkazak commented Oct 15, 2021

I installed the 0.6.0 version of Rancher Desktop for OSX, I got the same issue however on reinstalling the issue did not occur after the second installation. Also I can confirm that the permissions dialog box did not show up!

@jandubois
Copy link
Member

@rkazak Thank you for confirming!

You should not have gotten an error on the first install, but since you have done a successful install afterwards, there will be no logs around to investigate what happened, so nothing to investigate. I assume this issue then can be closed now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working platform/macos
Projects
None yet
Development

No branches or pull requests

4 participants