Issues with node creation about docker-machine-driver-hetzner HOT 4 CLOSED

Hi, sorry for the issues you encounter.

Is the different machine driver used at all?

An easy test for this would be to simply rename the machine driver binary -- if no error regarding a missing executable occurs, then most likely no, the different driver is not used.

How to fix the issues?

Sounds mostly like a ranger problem to me, but could you perhaps try and create the node manually using only docker-machine and the SSH key, image ids etc. you want? If that works, the error is somewhere else, if not, could you provide a full log of the provisioning output somewhere please?

from docker-machine-driver-hetzner.

Thanks for the quick reply. I will try to get the infos from the rancher instance.

from docker-machine-driver-hetzner.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

from docker-machine-driver-hetzner.

I'm facing a very similar issue.
I was the hetzner-driver v2.1.0 withing Rancher, saw this error while automatic re-creating new nodes BUT for Datacentres Nuremberg and Falkenstein.
I updated the driver to the v3.7.1 but still got the same error.
So I got the cluster created with a few nodes, but unable to add new nodes just yet.

from docker-machine-driver-hetzner.