Ignition files are JSON formatted provisioning instructions for container-centric operating systems such as Fedora CoreOS (FCOS) and Flatcar Linux. Ignition can configure system components like storage, filesystems, systemd units, and users. Ignition runs one time, during the first boot of the system.
When you provision an FCOS server at Vultr, you must supply an Ignition file in the customer portal. Ignition files are created by transpiling Fedora CoreOS Configuration (FCC) files with the Fedora CoreOS Config Transpiler,
As a simple example, create a file named example.fcc with the following contents. Replace ssh-rsa AAAA... with a public SSH key.
variant: fcos version: 1.0.0 passwd: users: - name: example_user ssh_authorized_keys: - ssh-rsa AAAA... groups: [ sudo, docker ]
This basic FCC file instructs Ignition to create a user named example_user as a member of the sudo and docker groups. The user can SSH to the server with a matching private SSH key. Next, this file must be compiled to Ignition format with
fcct utility is available for Linux, macOS, and Windows. Follow these installation steps for your platform. Windows users may install Gpg4win to verify the file signature. This example uses Linux x86_64 architecture.
$ wget https://getfedora.org/static/fedora.gpg
Import the keys to gpg.
$ gpg --import fedora.gpg
Download the detached signature.
Verify the download.
$ gpg --verify fcct-x86_64-unknown-linux-gnu.asc fcct-x86_64-unknown-linux-gnu
Make the file executable.
$ chmod +x fcct-x86_64-unknown-linux-gnu
Compile the file with the fcct utility. This example is for x86_64 Linux.
$ ./fcct-x86_64-unknown-linux-gnu -o example.ign example.fcc
Copy the contents of your example.ign file to the Ignition field.
Select your deployment options and click Deploy Now.
Find more information about Ignition and FCC at the official Fedora CoreOS site.