You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ tar -xvf docker-machine-driver-hetzner_3.1.0_linux_amd64.tar.gz
20
20
21
21
# Make it executable and copy the binary in a directory accessible with your $PATH
22
22
$ chmod +x docker-machine-driver-hetzner
@@ -98,6 +98,7 @@ $ docker-machine create \
98
98
-`--hetzner-existing-key-path`: Use an existing (local) SSH key instead of generating a new keypair. If a remote key with a matching fingerprint exists, it will be used as if specified using `--hetzner-existing-key-id`, rather than uploading a new key.
99
99
-`--hetzner-existing-key-id`: **requires `--hetzner-existing-key-path`**. Use an existing (remote) SSH key instead of uploading the imported key pair,
100
100
see [SSH Keys API](https://docs.hetzner.cloud/#resources-ssh-keys-get) for how to get a list
101
+
-`--hetzner-additional-key`: Upload an additional public key associated with the server, or associate an existing one with the same fingerprint. Can be specified multiple times.
101
102
-`--hetzner-user-data`: Cloud-init based User data
102
103
-`--hetzner-volumes`: Volume IDs or names which should be attached to the server
103
104
-`--hetzner-networks`: Network IDs or names which should be attached to the server private network interface
0 commit comments