-
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
Minikube 1.2.0 driver=none output not user-friendly #4615
Comments
Thank you for creating this issue, I believe we recently merged a PR that sugests user to run it with sudo. I think it will be in the next release. |
First issue is #4462 |
closing in favor of #4615 |
When I do |
Sounds like a bug, it should only copy those files for the none driver (which is not supposed to warn) |
The exact command to reproduce the issue: minikube start --vm-driver=none
The full output of the command that failed: 😄 minikube v1.2.0 on linux (amd64)
🔥 Creating none VM (CPUs=2, Memory=2048MB, Disk=20000MB) ...
🐳 Configuring environment for Kubernetes v1.15.0 on Docker
▪ kubelet.resolv-conf=/run/systemd/resolve/resolv.conf
💾 Downloading kubeadm v1.15.0
💾 Downloading kubelet v1.15.0
💣 Failed to update cluster: downloading binaries: copying kubeadm: copy: error creating file at /usr/bin/kubeadm: open /usr/bin/kubeadm: permission denied
😿 Sorry that minikube crashed. If this was unexpected, we would love to hear from you:
👉 https://github.com/kubernetes/minikube/issues/new
The output of the
minikube logs
command:The operating system version: Ubuntu 19.04
Comments:
sudo
, if Permission Denied error was thrown, minikube output could gently inform that this mode requires sudo to work instead of saying if crashed.minikube delete
none: can't delete cluster: output: sudo: kubeadm: command not found #4616.The text was updated successfully, but these errors were encountered: