Created
October 28, 2018 01:46
-
-
Save naoko/66b042235604702d924ac2b8f3f523ee to your computer and use it in GitHub Desktop.
Minikube without vm-driver
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
$ sudo minikube - vm-driver none start | |
[sudo] password for naoko: | |
Starting local Kubernetes v1.10.0 cluster… | |
Starting VM… | |
Getting VM IP address… | |
Moving files into cluster… | |
Setting up certs… | |
Connecting to cluster… | |
Setting up kubeconfig… | |
Starting cluster components… | |
Kubectl is now configured to use the cluster. | |
=================== | |
WARNING: IT IS RECOMMENDED NOT TO RUN THE NONE DRIVER ON PERSONAL WORKSTATIONS | |
The 'none' driver will run an insecure kubernetes apiserver as root that may leave the host vulnerable to CSRF attacks | |
When using the none driver, the kubectl config and credentials generated will be root owned and will appear in the root home directory. | |
You will need to move the files to the appropriate location and then set the correct permissions. An example of this is below: | |
sudo mv /root/.kube $HOME/.kube # this will write over any previous configuration | |
sudo chown -R $USER $HOME/.kube | |
sudo chgrp -R $USER $HOME/.kube | |
sudo mv /root/.minikube $HOME/.minikube # this will write over any previous configuration | |
sudo chown -R $USER $HOME/.minikube | |
sudo chgrp -R $USER $HOME/.minikube | |
This can also be done automatically by setting the env var CHANGE_MINIKUBE_NONE_USER=true | |
Loading cached images from config file. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment