Provisioning Fedora CoreOS on Exoscale

This guide shows how to provision new Fedora CoreOS (FCOS) instances on Exoscale Cloud Hosting.


Before provisioning an FCOS machine, it is recommended to have an Ignition configuration file containing your customizations. If you do not have one, see Producing an Ignition File.

Fedora CoreOS has a default core user that can be used to explore the OS. If you want to use it, finalize its configuration by providing e.g. an SSH key.

If you do not want to use Ignition to get started, you can make use of the Afterburn support..

You also need to have access to an Exoscale account. Register if you don’t have one.

Uploading an FCOS image as a custom Template

Exoscale offers official FCOS templates, but they are currently out of date. For now, we recommend creating your own template. Track progress on fixing this in #1166.

Exoscale provides Custom Templates to be able to upload any cloud image. To create a Custom Template you first need to download and decompress the image.

Download and decompress the QCOW2 image with coreos-installer
coreos-installer download -d -s "${STREAM}" -p exoscale -f qcow2.xz

Alternatively, QCOW2 images can be downloaded from the download page and manually decompressed.

Next you can Register a Custom Template. This can be done from the Web Portal or the Exoscale CLI. Either option requires the uncompressed image to be uploaded somewhere public and for the URL and an MD5 checksum to be provided during registration. One option is to use the object storage provided by Exoscale to host the image.

Upload to Object Storage and create Custom Template
# Set the version and calcuate the checksum
CHECKSUM=$(md5sum $FILE | cut -d " " -f 1)

# Upload to object storage
exo storage mb "sos://${BUCKET}"
exo storage upload --acl public-read $FILE "sos://${BUCKET}/image-import/"

# Create the template using given URL and CHECKSUM
URL=$(exo storage show "sos://${BUCKET}/image-import/$FILE" --output-template "{{.URL}}")
exo compute instance-template register --boot-mode=uefi $TEMPLATE $URL $CHECKSUM

You can then view the template using exo compute instance-template show --visibility=private $TEMPLATE.

Launching a VM instance

You can provision a FCOS instance using the Exoscale Web Portal or via the Exoscale CLI.

You will need to use at least version v1.54.0 of the Exoscale CLI.
Do not use the --cloud-init-compress argument to the CLI. It causes the Ignition config to be passed compressed to the instance and Ignition doesn’t tolerate that.
Add your ssh-key
exo compute ssh-key register key-name /path/to/key
Launching a new instance with Exoscale CLI
DISK='10' # in GiB
TEMPLATE=$TEMPLATE # template name set above
exo compute instance create $NAME \
    --disk-size $DISK \
    --ssh-key $SSHKEY \
    --template $TEMPLATE \
    --template-visibility private \
    --cloud-init "path/to/ignition-file.ign"
If just SSH access is desired and no further customization is required, you don’t need to pass any Ignition file and can omit the --cloud-init argument.
You can find out the instance’s assigned IP by running exo compute instance show $NAME

You now should be able to SSH into the instance using the associated IP address.

Example connecting
ssh core@<ip address>