Installation¶

The whole provisioning happens at first boot: you describe the server in metaconfig.yaml, render it into a Butane configuration, and hand that configuration to the standard Fedora CoreOS installer. Nothing has to be configured over SSH afterwards.

1. Edit metaconfig.yaml¶

• Each top-level key corresponds to a service or feature implemented as a template.
• Remove the keys you do not want.
• Fill in the parameters of the ones you keep, as described in the templates documentation.

The core key is mandatory: without an authorized SSH key there is no way to administer the server.

2. Generate the Butane configuration¶

python build_config.py metaconfig.yaml

This renders one template per key of metaconfig.yaml, merges the results and writes config.bu. Rendering stops with the template file and line number on the first missing or misspelled parameter.

3. Proceed with the standard FCOS installation workflow¶

Convert the configuration from Butane to Ignition and host it on the local network:

docker run --interactive --rm quay.io/coreos/butane:release --pretty --strict < config.bu > config.ign && python -m http.server 8000

Boot the Fedora CoreOS live ISO on the server and install, replacing the device and the address of the machine hosting the file as appropriate:

sudo coreos-installer install /dev/xxx --ignition-url http://192.168.xxx.xxx:8000/config.ign --insecure-ignition && sudo reboot

The server provisions itself during the first boot. Container images are pulled at that point, so the first start of each service takes a few minutes.

Next steps¶

• Maintenance explains how to log in, check services and read their logs.
• The design rationale describes what the generated configuration puts on the system.