-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Add important requirements to none driver page #7905
Labels
co/none-driver
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
kind/documentation
Categorizes issue or PR as related to documentation.
os/linux
priority/important-longterm
Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Comments
Here is the current output, with --driver=none:
When using another driver, it instead looks like:
|
Closed
This was referenced May 12, 2020
This was referenced May 19, 2020
This was referenced Jun 8, 2020
This was referenced Jun 15, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
co/none-driver
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
kind/documentation
Categorizes issue or PR as related to documentation.
os/linux
priority/important-longterm
Important over the long term, but may not be staffed and/or may need multiple releases to complete.
We now link to the kubeadm documentation directly from https://minikube.sigs.k8s.io/docs/drivers/none/, which is good. But we should list some of the more important requirements from
kubeadm
explicitly:2 CPU
2200M RAM available
iptables (in legacy mode)
conntrack (and others?)
SELinux permissive
Downgrade to cgroups v1
Maybe we should rephrase "VM" as something virtual or physical:
This should probably say "container runtime" instead of just Docker. Also need to install
crictl
At least when we fix the bug that all runtimes currently require a
docker
binary in order to startMost of these should probably be validated, and give helpful messages.
This to cut down on the number of identical support issues being opened.
The text was updated successfully, but these errors were encountered: