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
Copy file name to clipboardExpand all lines: README.md
+13-4Lines changed: 13 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -91,8 +91,8 @@ $ docker-machine create \
91
91
## Options
92
92
93
93
-`--hetzner-api-token`: **required**. Your project-specific access token for the Hetzner Cloud API.
94
-
-`--hetzner-image`: The name (or ID) of the Hetzner Cloud image to use, see [Images API](https://docs.hetzner.cloud/#resources-images-get) for how to get a list (defaults to `ubuntu-18.04`).
95
-
-`--hetzner-image`: The architecture to use during image lookup, inferred from the server type if not explicitly given.
94
+
-`--hetzner-image`: The name (or ID) of the Hetzner Cloud image to use, see [Images API](https://docs.hetzner.cloud/#resources-images-get) for how to get a list (currently defaults to `ubuntu-20.04`). *Explicitly specifying an image is **strongly** recommended and will be **required from v6 onwards***.
95
+
-`--hetzner-image-arch`: The architecture to use during image lookup, inferred from the server type if not explicitly given.
96
96
-`--hetzner-image-id`: The id of the Hetzner cloud image (or snapshot) to use, see [Images API](https://docs.hetzner.cloud/#resources-images-get) for how to get a list (mutually excludes `--hetzner-image`).
97
97
-`--hetzner-server-type`: The type of the Hetzner Cloud server, see [Server Types API](https://docs.hetzner.cloud/#resources-server-types-get) for how to get a list (defaults to `cx11`).
98
98
-`--hetzner-server-location`: The location to create the server in, see [Locations API](https://docs.hetzner.cloud/#resources-locations-get) for how to get a list.
@@ -125,6 +125,9 @@ When `--hetzner-image` is passed, lookup will happen either by name or by ID as
125
125
architecture, which is usually inferred from the server type. One may explicitly specify it using `--hetzner-image-arch` in which case the user
126
126
supplied value will take precedence.
127
127
128
+
While there is currently a default image as fallback, this behaviour will be removed in a future version. Explicitly specifying an operating system
129
+
image is strongly recommended for new deployments, and will be mandatory in upcoming versions.
130
+
128
131
#### Existing SSH keys
129
132
130
133
When you specify the `--hetzner-existing-key-path` option, the driver will attempt to copy `(specified file name)`
*`--hetzner-user-data-from-file` will be fully deprecated and its flag description will only read 'DEPRECATED, legacy'; current fallback behaviour will be retained. `--hetzner-flag-user-data-file` should be used instead.
251
255
*`--hetzner-disable-public-4`/`--hetzner-disable-public-6` will be fully deprecated and its flag description will only read 'DEPRECATED, legacy'; current fallback behaviour will be retained. `--hetzner-disable-public-ipv4`/`--hetzner-disable-public-ipv6` should be used instead.
252
256
253
257
### 5.0.0
254
258
255
259
*`--hetzner-user-data-from-file` will be removed entirely, including its fallback behavior
256
260
*`--hetzner-disable-public-4`/`--hetzner-disable-public-6` ill be removed entirely, including their fallback behavior
261
+
* not specifying `--hetzner-image` will generate a warning stating 'use of default image is DEPRECATED'
262
+
263
+
### 6.0.0
264
+
265
+
* specifying `--hetzner-image` will be mandatory, and a default image will no longer be provided
0 commit comments