Waiting for SSH to be available... #263
Comments
|
Hey, What type of system are you on? (Linux, OSX, etc.). One idea: it looks like minikube is re-using an existing host-only network adapter for you. Could you try deleting it using the virtualbox UI or cmd line tool? Something like this should work:
|
|
hello, I am on arch linux |
|
To confirm you have vt-x enabled, can you attach the output of:
Also please paste the output of:
|
|
Also please attach the logs from: |
|
You might want to write a troubleshooting doc. And put a link to it in ISSUE_TEMPLATE
|
``` 00:00:36.892758 NAT: IPv6 not supported |
|
By chance, are you running any kind of network proxy or VPN? |
|
Same behavior, setup:
Out of curiosity, after running
It seems to be trying to ssh to my local linux install (the host OS), I don't have a docker user in
VirtualBox UI has one interface on NAT and the second one as Host-Only-Adapter mode, changing the NAT one to Host-Only-Adapter or making it only one Host-Only-Adapter makes no difference.
This is my current config: seb@amon:[/home/seb]$ ip a l
3: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 02:42:90:2f:9d:a0 brd ff:ff:ff:ff:ff:ff
inet 172.17.0.1/16 scope global docker0
valid_lft forever preferred_lft forever
4: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 24:0a:64:f5:52:d8 brd ff:ff:ff:ff:ff:ff
inet 192.168.8.101/24 brd 192.168.8.255 scope global wlp3s0
valid_lft forever preferred_lft forever
inet6 fe80::798f:8bb7:c3a1:e117/64 scope link
valid_lft forever preferred_lft forever
5: vboxnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 0a:00:27:00:00:00 brd ff:ff:ff:ff:ff:ff
inet 192.168.99.1/24 brd 192.168.99.255 scope global vboxnet0
valid_lft forever preferred_lft forever
inet 192.168.99.100/24 brd 192.168.99.255 scope global secondary vboxnet0
valid_lft forever preferred_lft forever
inet6 fe80::aca7:69d4:eddf:a9b9/64 scope link
valid_lft forever preferred_lft foreverIf I show minikubeVM boot2docker from virtualbox UI, I can see 192.168.99.101 has been assigned to eth1 |
|
@dlorenc if i use network proxy？ how can i fix it？ |
|
All of a sudden I am getting this ...heck bhaskar@Fedora_16:50:49_Wed Aug 31:~>minikube start bhaskar@Fedora_17:13:36_Wed Aug 31:~>ps -ef | grep virtualbox I ran a rm -rf on .minikube dir to start afresh ..few times too Look like it stuck here for eternity ...heck bhaskar@Fedora_17:12:37_Wed Aug 31:~>minikube start --show-libmachine-logs and the process shows bhaskar@Fedora_17:20:37_Wed Aug 31:~>ps -ef | grep minikube And it failed virtually E0831 17:21:40.655906 2080 start.go:78] Error starting host: Error configuring auth on host: Too many retries waiting for SSH to be available. Last error: Maximum number of retries (60) exceeded |
|
Well, it works! I made a mistake, I ran several os in different physical partition ,and a common LVM home to all . I updated the minikube version last night on one of them and then back to other OS today ..in turn when I started to run ..it corrupted the .minikube folder as well version conflict giving that error ..probably ..here is the outcome now ... I have downloaded minikube 0.8 ...it was 0.7 ..:) ` This machine has been allocated an IP address, but Docker Machine could not SSH for the machine should still work, but connecting to exposed ports, such as You may need to add the route manually, or use another related workaround. This could be due to a VPN, proxy, or host file configuration issue. You also might want to clear any VirtualBox host only interfaces you are not using. To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'. |
|
I run into a similar issue (too many retries). But I discover the problem is that minikube has built-in logic to choose either GO implmentation of SSH or external SSH command (in a shell). The external one is not always compatible. I would recommend force minikube to use Go implmenetaiton of SSH than letting external env to affect the behavior. My case. Minikube on win7. Under windows CMD, this command works. (minikube) DBG | Host-only MAC: 080027741666 But when minikube is run under cygwin (Mobaxterm), it fails and the verbose log shows: (minikube) DBG | Host-only MAC: 080027741666 (minikube) DBG | SSH cmd err, output: fork/exec C:\Users\fyang\AppData\Local\Temp\Mxt90\bin\ssh.exe: This version of %1 is not compatible with the version of Windows you're running. Check your computer's system information to see whether you need a x86 (32-bit) or x64 (64-bit) version of the program, and then contact the software publisher.: By renaming the Mobaxterm SSH to something else, minikube start works too (so does minikube ip). Recommendation: minikube should always use built-in GO implementation of SSH. |
|
I think these issues have been fixed. |
|
I ran into this issue during installation because I tried to start minikube before Kubectl had finished installing. Minikube complained and told me to go install Kubectl but went right on trying to run anyway. The only way to fix it was to run This reset everything and it started right up. |
|
@todaywasawesome I installed kubectl and minikubes, then ran the minikube start command and an error that i needed to turn on VT-x in the bios. After doing so, i got the error:
Running |
|
I had the same issue described above on Ubuntu 16.04 after installing |
|
Hi, seems like minikube still doesn't use his own ssh implementation: minikube version: v0.18.0 I have OpenSSH installed (windows 7 64bit) but I can't uninstall it to force minikube work :) Any ideas? |
|
well, if i override the PATH in current session with "set PATH=c:" so it doesn't find the OpenSSH binary, minikube works :) . I think it's worth fixing this issue, should be a really small adjustment - to avoid using any other external ssh command even if it exists in PATH. |
|
I had this issue today with minicube 0.21: I didn't install kubectl until after I ran |
|
I was able to fix this by installing cfssl and removing |
|
Minikube uses system ssh by default. But windows system don't have a ssh by default. Try using git bash as terminal have try. If it is not work, try re-install git bash as system ssh client. |
|
@jevy-wangfei I run cmd in git bash with admin.
I get this error:
and it will try again and again. Any ideal? |
|
Does the switch you have created come with a DHCP server?
Either create an external switch, or setup a DHCP server on the same
segment.
Since I see an IPv6 address, it surely did not get the right address. Note:
IPv6 is not supported at this moment.
|
|
@jevy-wangfei installing a SSH client is not necessary, as there is a fallback mode to use a native implementation. Besides, git-bash is not well supported, so it would be advisable to install the openssh-win32 installs (tested with minishift and minikube to work as expected). |
If problem persists, please create a new issuethis issue has been closed and might not be up-to-date |
Hey,
I am triyng to create minikube but is fails with
any help would be appreciate
The text was updated successfully, but these errors were encountered: