Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Minikube install in Ubuntu vm_VT-X/AMD-v enabling to VM inside another VM [closed]

Tags:

I'm tring to install minikube in Ubuntu vm (in virtual box). I have enabled VT-X/AMD-v for the vm. But i'm getting following error.

# minikube start
Starting local Kubernetes cluster...
E0217 15:00:35.395801    3869 start.go:107] Error starting host: Error creating host: Error with pre-create check: "This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory".

 Retrying.
E0217 15:00:35.396019    3869 start.go:113] Error starting host:  Error creating host: Error with pre-create check: "This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory"
================================================================================
An error has occurred. Would you like to opt in to sending anonymized crash
information to minikube to help prevent future errors?
To opt out of these messages, run the command:
    minikube config set WantReportErrorPrompt false
================================================================================
Please enter your response [Y/n]:

I found a reference, according to that, we can not have virtualization inside virtualization. Is it true? How can i fix this?

like image 513
Lakmal Vithanage Avatar asked Feb 17 '17 09:02

Lakmal Vithanage


People also ask

Does minikube require VM?

You can work on Minikube even without installing VirtualBox. Minikube also supports a --driver=none option that runs the Kubernetes components on the host and not in a VM. Using this driver requires Docker and a Linux environment but not a hypervisor. If you're using the none driver in Debian or a derivative, use the .

How do you check minikube is installed or not?

Once your minikube is running, you can use kubectl version command to see the version of kubernetes server. Also, when you start minikube using minikube start , kubernetes version is shown in stdout. $ minikube start Starting local Kubernetes v1. 6.0 cluster...


3 Answers

Virtual Box does not support VT-X/AMD-v in nested virtualisation. See this open ticket/feature request on virtualbox.org.

There are also some more questions and answers here on SO discussing this topic.

Possible solutions:

  1. As already mentioned: Use a different hypervisor that does support VT-X/AMD-v in nested virtualisation (like Xen, KVM or VMware).
  2. Install Minikube on the host OS and not in a VM.
  3. Run Minikube directly using Docker and the "none" driver option as described in Tad Guskis answer.
like image 193
Phonolog Avatar answered Sep 28 '22 01:09

Phonolog


Run Minikube directly on the VM using Docker and the "none" driver option which does not require nested virtualization.

Set the none driver option:

[root@minikube ~]# minikube config set vm-driver none

Install Docker-ce following instructions for your VM OS version.

Lastly run minikube start:

[root@minikube ~]# systemctl enable docker
Created symlink from /etc/systemd/system/multi-user.target.wants/docker.service to /usr/lib/systemd/system/docker.service.
[root@minikube ~]# systemctl start docker
[root@minikube ~]# minikube start
Starting local Kubernetes v1.10.0 cluster...
Starting VM...
Getting VM IP address...
Moving files into cluster...
Downloading kubeadm v1.10.0
Downloading kubelet v1.10.0
Finished Downloading kubelet v1.10.0
Finished Downloading kubeadm v1.10.0
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.
like image 24
Tad Guski Avatar answered Sep 27 '22 01:09

Tad Guski


Try running minikube without nested virtualization (docker should be installed):

minikube start --vm-driver=none

From Kubernetes documentation:

Minikube also supports a --vm-driver=none option that runs the Kubernetes components on the host and not in a VM. Using this driver requires Docker and a linux environment, but not a hypervisor.

like image 7
k13i Avatar answered Sep 27 '22 01:09

k13i