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
Unable to start minikube with --extra-config 'apiserver.cors-allowed-origins=["http://*"]' on mac #4477
Comments
I've seen similar issues. minikube start --extra-config=apiserver.v=10 --vm-driver hyperkit --extra-config 'apiserver.cors-allowed-origins=["http://"]' /default ⎈ 💣 Error starting cluster: cmd failed: sudo /usr/bin/kubeadm init --config /var/lib/kubeadm.yaml --ignore-preflight-errors=DirAvailable--etc-kubernetes-manifests,DirAvailable--data-minikube,FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml,FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml,FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml,FileAvailable--etc-kubernetes-manifests-etcd.yaml,Port-10250,Swap : Process exited with status 1 😿 Sorry that minikube crashed. If this was unexpected, we would love to hear from you: |
I bet this issue is due to a lack of quoting when we generate the kubeadm YAML. The fix is likely to be adding double quotes around {{$val}} for the different kubeadm templates, such as:
If you have a chance, give it a try and I'll be happy to review the PR. Help wanted! |
It was indeed an issue w/ quotes. The following worked:
Unfortunately, I'm unable to open a PR to fix this (long story). |
One hint regarding
|
Closing as a workaround appears to have been found. |
Related: #4806 |
Thanks for the hint. I have been searching for a solution to access the apiserver for days and it works like a charm! |
Complete cmd+output:
Output minikube logs:
minikube-logs.txt
The operating system version:
The text was updated successfully, but these errors were encountered: