ssh never becomes available about docker-machine-vultr

[EugenMayer]

Just in case, that helps, upgraded to your machine driver version 1.4, but still getting the same issue

while ssh already works

ssh [email protected]
[rancher@w2 ~]$

[EugenMayer]

Could it be related to the fact that i do not use a reservedIpID at all so rancher does not know the IP of the host being setup by vultr?

My data is:
region: 9 (Frankfurt)
ssh-key:
rancherosversion: 1.1.1
apikey:

anything else is blank / default

[EugenMayer]

Last information, adding the host using the vultr driver, then removing the host in the rancher GUI, then ssh'ing into the host and using "custom host" to deploy a rancher agent will properly register the host with the rancher server. So there is basically all setup, just SSH seems to be broken.

What i ask myself though is, how is the machine-driver actually SSH-ing without having my SSH private key - i guess the ssh connection is used to deploy the rancher agent? Is a vultr api used for that? Kind of makes no sense here

[byjg]

I created the machine outside the Rancher GUI using the vultr machine driver 1.4.0 with the command below:

docker-machine create \
     --driver vultr --vultr-api-key=00000000 \
     --vultr-private-networking=true --vultr-ssh-key-id 0000000000 \
     my-machine

The machine was created and the SSH is OK. I can connect with the user "rancher" in the machine.

In the Rancher GUI interface I leave all parameters blank except the parameters I setup above.

So the list of problems I notice / have:

• Rancher GUI is passing some king of parameter to Vultr Docker Machine Driver that the Vultr Driver does not recognize and it is causing the error;
• The default user is "rancher" but in the Rancher GUI interface is "root" (This is only a note)
• The interface eth1 on the machine created is UP but does not have any IP. I had to setup manually.

Version of the software I used:

• Vultr Docker Machine Driver: 1.4.0
• Ranche Server: v1.6.13

[EugenMayer]

thanks to @superseb who found out that this can be fixed by just not providing a ssh-key at all!

[egadgetjnr]

Unfortunately the suggestion by @superseb doesn't work for me.

I've tried all combinations and keep getting the same issue of ssh not being available on the latest version of Rancher Server (v 2.0.2)

Any other suggestions?