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

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 dockerCreated 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 startStarting local Kubernetes v1.10.0 cluster...Starting VM...Getting VM IP address...Moving files into cluster...Downloading kubeadm v1.10.0Downloading kubelet v1.10.0Finished Downloading kubelet v1.10.0Finished Downloading kubeadm v1.10.0Setting 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 attacksWhen 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/.minikubeThis can also be done automatically by setting the env var CHANGE_MINIKUBE_NONE_USER=trueLoading cached images from config file.

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.

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.