osbuild-composer works with a concept of blueprints. A blueprint is a description of the final image and its customizations. A customization can be:
- an additional RPM package
- enabled service
- custom kernel command line parameter, and many others. See Blueprint reference for more details.
An image is defined by its blueprint and image type, which is for example
qcow2 (QEMU Copy On Write disk image) or
AMI (Amazon Machine Image).
name = "base-image-with-tmux" description = "A base system with tmux" version = "0.0.1" [[packages]] name = "tmux" version = "*"
The blueprint is in TOML format.
osbuild-composer provides a storage for blueprints. To store a
blueprint.toml blueprint file, run this command:
$ composer-cli blueprints push blueprint.toml
To verify that the blueprint is available, list all currently stored blueprints:
$ composer-cli blueprints list base-image-with-tmux
To display the blueprint you have just added, run the command:
$ sudo composer-cli blueprints show base-image-with-tmux name = "base-image-with-tmux" description = "A base system with tmux" version = "0.0.1" modules =  groups =  [[packages]] name = "tmux" version = "*"
osbuild-composer supports various types of output images. To see all supported types, run this command:
$ composer-cli compose types