This library adds the support for creating Docker machines hosted on the Hetzner Cloud.
You need to create a project-specific access token under Access > API Tokens in the project control panel
and pass that to docker-machine create with the --hetzner-api-token option.
You can find sources and pre-compiled binaries here.
# Download the binary (this example downloads the binary for linux amd64)
$ wget https://github.com/JonasProgrammer/docker-machine-driver-hetzner/releases/download/2.1.0/docker-machine-driver-hetzner_2.1.0_linux_amd64.tar.gz
$ tar -xvf docker-machine-driver-hetzner_2.1.0_linux_amd64.tar.gz
# Make it executable and copy the binary in a directory accessible with your $PATH
$ chmod +x docker-machine-driver-hetzner
$ cp docker-machine-driver-hetzner /usr/local/bin/$ docker-machine create \
--driver hetzner \
--hetzner-api-token=QJhoRT38JfAUO037PWJ5Zt9iAABIxdxdh4gPqNkUGKIrUMd6I3cPIsfKozI513sy \
some-machine$ HETZNER_API_TOKEN=QJhoRT38JfAUO037PWJ5Zt9iAABIxdxdh4gPqNkUGKIrUMd6I3cPIsfKozI513sy \
&& HETZNER_IMAGE=centos-7 \
&& docker-machine create \
--driver hetzner \
some-machineIf you use an image without aufs, like the one currently supplied with the debian-9 image, you can try specifying another storage driver, such as overlay2. Like so:
$ docker-machine create \
--engine-storage-driver overlay2 \
--driver hetzner \
--hetzner-image debian-9 \
--hetzner-api-token=QJhoRT38JfAUO037PWJ5Zt9iAABIxdxdh4gPqNkUGKIrUMd6I3cPIsfKozI513sy \
some-machine$ CLOUD_INIT_USER_DATA=`cat <<EOF
#cloud-config
write_files:
- path: /test.txt
content: |
Here is a line.
Another line is here.
EOF
`
$ docker-machine create \
--driver hetzner \
--hetzner-api-token=QJhoRT38JfAUO037PWJ5Zt9iAABIxdxdh4gPqNkUGKIrUMd6I3cPIsfKozI513sy \
--hetzner-user-data="${CLOUD_INIT_USER_DATA}" \
some-machineAssuming your snapshot ID is 424242:
$ docker-machine create \
--driver hetzner \
--hetzner-api-token=QJhoRT38JfAUO037PWJ5Zt9iAABIxdxdh4gPqNkUGKIrUMd6I3cPIsfKozI513sy \
--hetzner-image-id=424242 \
some-machine--hetzner-api-token: required. Your project-specific access token for the Hetzner Cloud API.--hetzner-image: The name of the Hetzner Cloud image to use, see Images API for how to get a list (defaults toubuntu-18.04).--hetzner-image-id: The id of the Hetzner cloud image (or snapshot) to use, see Images API for how to get a list (mutually excludes--hetzner-image).--hetzner-server-type: The type of the Hetzner Cloud server, see Server Types API for how to get a list (defaults tocx11).--hetzner-server-location: The location to create the server in, see Locations API for how to get a list.--hetzner-existing-key-path: Use an existing (local) SSH key instead of generating a new keypair.--hetzner-existing-key-id: requires--hetzner-existing-key-path. Use an existing (remote) SSH key instead of uploading the imported key pair, see SSH Keys API for how to get a list--hetzner-user-data: Cloud-init based User data--hetzner-volumes: Volume IDs or names which should be attached to the server--hetzner-networks: Network IDs or names which should be attached to the server private network interface--hetzner-use-private-network: Use private network
When you specify the --hetzner-existing-key-path option, the driver will attempt to copy (specified file name)
and (specified file name).pub to the machine's store path. They public key file's permissions will be set according
to your current umask and the private key file will have 600 permissions.
When you additionally specify the --hetzner-existing-key-id option, the driver will not create an SSH key using the API
but rather try to use the existing public key corresponding to the given id. Please note that during machine creation,
the driver will attempt to get the key and compare it's
fingerprint to the local public key's fingerprtint. Keep in mind that the both the local and the remote key must be
accessible and have matching fingerprints, otherwise the machine will fail it's pre-creation checks.
Also note that the driver will attempt to delete the linked key during machine removal, unless --hetzner-existing-key-id
was used during creation.
| CLI option | Environment variable | Default |
|---|---|---|
--hetzner-api-token |
HETZNER_API_TOKEN |
- |
--hetzner-image |
HETZNER_IMAGE |
ubuntu-18.04 |
--hetzner-image-id |
HETZNER_IMAGE_ID |
- |
--hetzner-server-type |
HETZNER_TYPE |
cx11 |
--hetzner-server-location |
HETZNER_LOCATION |
- (let Hetzner choose) |
--hetzner-existing-key-path |
HETZNER_EXISTING_KEY_PATH |
- (generate new keypair) |
--hetzner-existing-key-id |
HETZNER_EXISTING_KEY_ID |
0 (upload new key) |
--hetzner-user-data |
HETZNER_USER_DATA |
- |
--hetzner-networks |
HETZNER_NETWORKS |
- |
--hetzner-volumes |
HETZNER_VOLUMES |
- |
--hetzner-use-private-network |
HETZNER_USE_PRIVATE_NETWORK |
false |
Use an up-to-date version of Go to use Go Modules.
To use the driver, you can download the sources and build it locally:
# Enable Go Modules if you are not outside of your $GOPATH
$ export GO111MODULE=on
# Get sources and build the binary at ~/go/bin/docker-machine-driver-hetzner
$ go get github.com/jonasprogrammer/docker-machine-driver-hetzner
# Make the binary accessible to docker-machine
$ export GOPATH=$(go env GOPATH)
$ export GOBIN=$GOPATH/bin
$ export PATH="$PATH:$GOBIN"
$ cd $GOPATH/src/jonasprogrammer/docker-machine-driver-hetzner
$ go build -o docker-machine-driver-hetzner
$ cp docker-machine-driver-hetzner /usr/local/bin/docker-machine-driver-hetznerFork this repository, yielding github.com/<yourAccount>/docker-machine-driver-hetzner.
# Get the sources of your fork and build it locally
$ go get github.com/<yourAccount>/docker-machine-driver-hetzner
# * This integrates your fork into the $GOPATH (typically pointing at ~/go)
# * Your sources are at $GOPATH/src/github.com/<yourAccount>/docker-machine-driver-hetzner
# * That folder is a local Git repository. You can pull, commit and push from there.
# * The binary will typically be at $GOPATH/bin/docker-machine-driver-hetzner
# * In the source directory $GOPATH/src/github.com/<yourAccount>/docker-machine-driver-hetzner
# you may use go get to re-build the binary.
# * Note: when you build the driver from different repositories, e.g. from your fork
# as well as github.com/jonasprogrammer/docker-machine-driver-hetzner,
# the binary files generated by these builds are all called the same
# and will hence override each other.
# Make the binary accessible to docker-machine
$ export GOPATH=$(go env GOPATH)
$ export GOBIN=$GOPATH/bin
$ export PATH="$PATH:$GOBIN"
# Make docker-machine output help including hetzner-specific options
$ docker-machine create --driver hetzner
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent