Website: Minikube error and issue with k8s.io/docs/getting-started-guides/minikube/

[mchawla16]

This is a...

• [ ] Feature Request
• [x] Bug Report

Problem:

1. VM driver is kvm
2. Minikube crashes if started without the --vm-driver=xxx flag

minikube start
Starting local Kubernetes v1.10.0 cluster...
Starting VM...
Downloading Minikube ISO
 150.53 MB / 150.53 MB [============================================] 100.00% 0s
E0509 04:37:28.149683    6430 start.go:159] Error starting host: Error creating host: Error executing step: Running precreate checks.
: VBoxManage not found. Make sure VirtualBox is installed and VBoxManage is in the path.

 Retrying.
E0509 04:37:28.150207    6430 start.go:165] Error starting host:  Error creating host: Error executing step: Running precreate checks.
: VBoxManage not found. Make sure VirtualBox is installed and VBoxManage is in the path
================================================================================
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]: 

If you wait to read the above error message, the command exits without the user input of Y/n.

Proposed Solution:

1. Minikube should not crash.
2. The error message
   E0509 04:37:28.149683 6430 start.go:159] Error starting host: Error creating host: Error executing step: Running precreate checks.: VBoxManage not found. Make sure VirtualBox is installed and VBoxManage is in the path.

could be improved so that it is simply like:

Error starting host: Error creating host: Error executing step: Running precreate checks.: VBoxManage not found. Make sure VirtualBox is installed and VBoxManage is in the path.

1. The command should wait for the user to enter Y/n.

2. The kubernetes page should be updated with information to install the kvm2 driver instead of kvm as using minikube with kvm gives the following warning:

WARNING: The kvm driver is now deprecated and support for it will be removed in a future release.
Please consider switching to the kvm2 driver, which is intended to replace the kvm driver.

Page to Update:
https://kubernetes.io/docs/getting-started-guides/minikube/

Kubernetes Version: v0.26.1(latest)

[Rajakavitha1]

@mchawla16 This has been documented in https://github.com/kubernetes/minikube/blob/master/docs/drivers.md#kvm-driver and the https://kubernetes.io/docs/getting-started-guides/minikube/#installation [kvm (driver installation)] does contain a link to https://github.com/kubernetes/minikube/blob/master/docs/drivers.md#kvm-driver

Please mark this as closed if it addresses the issue you raised.

[mchawla16]

Thanks @Rajakavitha1, The issue relates to the Quickstart section on the page https://kubernetes.io/docs/getting-started-guides/minikube/, which mentions that kvm should be installed and points to https://github.com/kubernetes/minikube/blob/master/docs/drivers.md#kvm-driver

I think this should be updated to install kvm2 instead and add the link https://github.com/kubernetes/minikube/blob/master/docs/drivers.md#kvm2-driver as using kvm gives the warning above. This will only address point 4 in above issue.

Please review the points 1-3 above as well and see if its possible to fix them. Thanks.

[benpriestman]

:+1:
For a first-time user, the fact that the quickstart points to a deprecated driver is misleading.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[tsoarescruz]

First install vm virtualization as virtual-box and this will resolved

[andradewagner]

Don't forget to enable the virtualization in BIOS. VT-d or Intel Virtualization technology... something like that. Generally in advanced area.