Failing with

[gerwinbrunner]

It seem that the newly spawned worker can't connect... any idea what goes wrong there?

Is it also possible to log into the worker somehow? I can connect in the hetzner console, but I don't know the user and/or password...

hetzner-runner_1  | Copying certs to the remote machine...              driver=hetzner name=runner-ux2alzk4-runner-1607630955-16c49b06 operation=create
hetzner-runner_1  | WARNING: Failed to process runner                   builds=0 error=failed to update executor: no free machines that can process builds executor=docker+machine runner=uX2ALzK4
hetzner-runner_1  | Setting Docker configuration on the remote daemon...  driver=hetzner name=runner-ux2alzk4-runner-1607630955-16c49b06 operation=create
hetzner-runner_1  | WARNING: Failed to process runner                   builds=0 error=failed to update executor: no free machines that can process builds executor=docker+machine runner=uX2ALzK4
hetzner-runner_1  | WARNING: Failed to process runner                   builds=0 error=failed to update executor: no free machines that can process builds executor=docker+machine runner=uX2ALzK4
hetzner-runner_1  | WARNING: Failed to process runner                   builds=0 error=failed to update executor: no free machines that can process builds executor=docker+machine runner=uX2ALzK4
hetzner-runner_1  | WARNING: Failed to process runner                   builds=0 error=failed to update executor: no free machines that can process builds executor=docker+machine runner=uX2ALzK4
hetzner-runner_1  | WARNING: Failed to process runner                   builds=0 error=failed to update executor: no free machines that can process builds executor=docker+machine runner=uX2ALzK4
hetzner-runner_1  | WARNING: Failed to process runner                   builds=0 error=failed to update executor: no free machines that can process builds executor=docker+machine runner=uX2ALzK4
hetzner-runner_1  | WARNING: Failed to process runner                   builds=0 error=failed to update executor: no free machines that can process builds executor=docker+machine runner=uX2ALzK4
hetzner-runner_1  | WARNING: Failed to process runner                   builds=0 error=failed to update executor: no free machines that can process builds executor=docker+machine runner=uX2ALzK4
hetzner-runner_1  | WARNING: Failed to process runner                   builds=0 error=failed to update executor: no free machines that can process builds executor=docker+machine runner=uX2ALzK4
hetzner-runner_1  | WARNING: Failed to process runner                   builds=0 error=failed to update executor: no free machines that can process builds executor=docker+machine runner=uX2ALzK4
hetzner-runner_1  | WARNING: Failed to process runner                   builds=0 error=failed to update executor: no free machines that can process builds executor=docker+machine runner=uX2ALzK4
hetzner-runner_1  | WARNING: Failed to process runner                   builds=0 error=failed to update executor: no free machines that can process builds executor=docker+machine runner=uX2ALzK4
hetzner-runner_1  | ERROR: Error creating machine: Error running provisioning: Unable to verify the Docker daemon is listening: Maximum number of retries (10) exceeded  driver=hetzner name=runner-ux2alzk4-runner-1607630955-16c49b06 operation=create
hetzner-runner_1  | WARNING: Problem while reading command output       error=read |0: file already closed
hetzner-runner_1  | WARNING: Machine creation failed, trying to provision  error=exit status 1 name=runner-ux2alzk4-runner-1607630955-16c49b06

[L-U-C-K-Y]

Hi @gerwinbrunner

There is an issue with the latest docker version, see here: docker/machine#4858 (comment)

You can resolve this bug, by specifying an older docker version in the config.toml:

 MachineOptions = [
      "engine-install-url=https://releases.rancher.com/install-docker/19.03.9.sh",
    ]

I'll add it to the README.

[chickahoona]

Took me 2 hours to fix it, and when I wanted to open an issue explaining the problem and solution I found this issue here ... Could have saved me 2 hours of my time :(

[mawalu]

I just merged the MR from @L-U-C-K-Y that adds a this fix to the README