Sascha Falk

Ok, it seems there is something strange going on. I've put bogus input into `HETZNER_VOLUMES` and `HETZNER_NETWORKS`, but no error pops up. I'm afraid the sha256 hash will not enlighten...

I've downloaded the prebuilt binaries for docker-machine and the Hetzner driver. My platform is Ubuntu 18.04 LTS (amd64) now. The following script... ``` #!/bin/bash export HETZNER_API_TOKEN='[[ REDACTED ]]' export HETZNER_IMAGE='ubuntu-18.04'...

Ok, I added `log.Infof(">>> NETWORKS: %s", networks)` before line 255 and `log.Infof(">>> VOLUMES: %s", volumes)` before line 266. Here is the result: ``` ... (some-machine) >>> NETWORKS: [] (some-machine) >>>...

Hmm, there is no driver I'm aware of. To be honest, I'm not a GO programmer, so tracking the issue down could become a bit tedious.

Thank you very much for your engagement, Jonas! I think I can work around the issue by mapping the environment variables to docker-machine command line parameters. This circumvents the problem...

Then the laurels go to you too, @mxschmitt. Good work and many thanks for the driver :-)

We're encountering the same issue. Is there any progress fixing it?

@ashwanthkumar Thank you for your response. Meanwhile we found a way to work without the plugin. We just wanted to build a set of release branches with a specific pattern...

@nishakm Thank you for your quick response. I'm afraid that kaniko does not work that way. Kaniko builds an image using a specific Dockerfile and pushes the resulting image straight...