-
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
SSH cmd err, output: exit status 255: #1882
Comments
Can you see if a |
I have try it with ~$ minikube delete
Deleting local Kubernetes cluster...
Machine deleted.
~$ minikube start
Starting local Kubernetes v1.7.0 cluster...
Starting VM...
Killed |
I can confirm this is also happening in Ubuntu, I believe the issue relies on that ssh command not pointing to where it should (or the node ssh not being available). My system layout is as follows: Vmwareplayer 6.0.5 build-2443746, hypervisor config enabled. |
the very same (minikube version: v0.22.3) in Ubuntu 16.04.3 with --vm-driver=none (docker 17.09.0-ce) Also, I've tried to delete and then start without luck. |
Issues go stale after 90d of inactivity. Prevent issues from auto-closing with an If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Rotten? LOL this has been going on for YEARS all the same codebase....... Three YEARS later I can generate the exact same errors via the broken SSH calling code across all the drivers, docker-machine, etc. Heck, now in 2018 you still cannot simply run the very 1st step and set up a brand new virtualbox (the default) docker-machine without generating it:
|
Three years later and it happened again using minikube v1.12.0 on Fedora 31 wish kvm2 driver.
I tried to run the ssh command from a different terminal, omitting the
In my case the output was: IMO, after the timeout happened, there could be another call without the |
BUG REPORT
Environment:
What happened:
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Output of
minikube logs
(if applicable):Anything else do we need to know:
The text was updated successfully, but these errors were encountered: