Ignition is the utility used by CoreOS Container Linux to manipulate disks during the initramfs. This includes partitioning disks, formatting partitions, writing files (regular files, systemd units, networkd units, etc.), and configuring users. On first boot, Ignition reads its configuration from a source of truth (remote URL, network metadata service, hypervisor bridge, etc.) and applies the configuration.

Ignition has two main development branches: master and spec2x. This is the spec2x branch which is for Ignition included in Container Linux. For new Ignition development see the master branch.

Odds are good that you don't want to invoke Ignition directly. In fact, it isn't even present in the Container Linux root filesystem. Take a look at the Getting Started Guide for details on providing Ignition with a runtime configuration.

• Mailing list: coreos-dev
• IRC: #coreos on freenode.org
• Bugs: issues

See CONTRIBUTING for details on submitting patches and the contribution workflow.

To help triage or fix bugs, see the current Ignition issues.

• To report a bug, use the bug tracker

To validate a config for Ignition there are binaries for a cli tool called ignition-validate available on the releases page, and an online validator available on the CoreOS website.

• Contributing Guidelines — How to contribute, find issues, and submit pull requests
• Code of Conduct — Standards for respectful and inclusive community participation
• Security Policy — How to report vulnerabilities and security-related information
• Maintainers — Current project maintainers and their responsibilities
• Governance — Project governance model, decision-making process, and roles