-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Windows "minikube start" fails with chmod permissions error. #1928
Comments
I've also seen this on an upgrade from version 0.21.0 to 0.22.0. Thankfully the cluster still worked on downgrade back to 0.21.0. |
I encountered exactly the same problem on Windows 10 using VirtualBox |
I also have the issue in the new version v0.22.0 on wndows10 |
yip, same here. previous comment to use os.Chmod rather than File.Chmod. Is this something I can do when running minikube start or is it more a note for how to fix the bug? |
This should be fixed in the latest point release Sorry about that |
I am using Minikube v0.21.0. Error:
|
I deleted the Minikube profile (.minikube folder) and then it worked properly again. |
I experienced the same on macOS after a manual downgrade from 0.22.x to 0.20.0. Per @abejenaru, deleting the .minikube dir resolved the issue. It may be worth looking at an adjustment to the error message that indicates that the .minikube dir needs to be recreated, rather than a generic permissions error. |
Environment: Windows 7, clean install.
Minikube version: v0.22.0
What happened:
From a clean install, after provisioning VM, multiple file errors occurred when attempting to chmod certificate files, and installation fails.
The relevant error from the log below is:
error changing file permissions for C:\Users\James\.minikube\ca.pem: chmod C:\Users\James\.minikube\ca.pem: not supported by windows
What you expected to happen:
The
ca.pem
files are installed without error and the installation continues successfully. This process works fine on v0.21.00.How to reproduce it:
.minikube
directory.minikube start --v=3
Output of
minikube logs
(if applicable):Anything else do we need to know:
Possibly related to this line which does the Chmod, which is not supported under Windows.
The text was updated successfully, but these errors were encountered: