4.2. RHEL image builder blueprint format

RHEL image builder supports blueprints in both the .toml and .json formats.

A typical blueprint file include the following elements:

The blueprint metadata

name = "<blueprint_name>"
description = "<long_form_description_text>"
version = "<version>"

The <blueprint_name> and <long_form_description_text> fields are the name and description for your blueprint.

The <version> is a version number according to the Semantic Versioning scheme, and is present only once for the entire blueprint file.

Groups to include in the image

[[groups]]
name = "<group_name>"

The <group_name> entry describes a group of packages to be installed into the image. Groups use the following package categories:

Mandatory
Default
Optional
The group-name is the name of the group, for example, anaconda-tools, widget, wheel, or users. Blueprints install the mandatory and default packages. There is no mechanism for selecting optional packages.

Packages to include in the image

[[packages]]
name = "<package_name>"
version = "<package_version>"

package-name is the name of the package, such as httpd, gdb-doc, or coreutils.

package-version is a version to use. This field supports dnf version specifications:

For a specific version, use the exact version number, such as 8.7.0.
For the latest available version, use the asterisk *.
For the latest minor version, use a format such as 8.*.
Repeat this block for every package to include.
注意
There are no differences between packages and modules in the RHEL image builder tool. Both are treated as RPM package dependencies.