Skip to content

The driver information should be on the Documentation page #20611

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

Open
beezerbt opened this issue Apr 12, 2025 · 0 comments
Open

The driver information should be on the Documentation page #20611

beezerbt opened this issue Apr 12, 2025 · 0 comments

Comments

@beezerbt
Copy link

What Happened?

The driver option of Minikube is _key to a fundamental understanding of getting Minikube up and running locally (in this case on a Windows 11 machine). Why? Because if the default which is using Docker fails (which it did for me after many tries) the Documentation page, having __not mentioned that there are __multiple ways of getting Minikube up and running locally, leaves the end user thinking that that is the only option and facing a brick wall.
Mentioning the "Container" or "Virtual Machine Manager" is so obtuse...no nube would ever even know why that is there.
Also, who has 2 CPU's and 2 Gig of free mem, or 20 gig of free disk space...this is totally misleading and immediately makes a first time visitor wanting to abandon and leave...not knowing that using the hyperV option would provide those.

Your documentation is woeful at best.

P.S> the docker option failed with some IAM issue that I looked up and solved, but then it failed with a networking issue.

Attach the log file

Log files is not relevant it is about the quality or lack of the documentation of the website.

Operating System

Windows

Driver

Docker

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant