Skip to content

Building an image from a custom manifest

Both AutoSD and its downstream RHIVOS are sets of RPM binaries. You customize and build your own image, including your own applications as RPMs or container images.

Automotive Image Builder builds those images on CentOS Stream, Fedora, or RHEL hosts, with the option to build immutable images using OSTree.

Use the automotive-image-builder tool to build an image from a custom Automotive Image Builder manifest file. Alternatively, use one of the available example Automotive Image Builder manifests to build an image:

  • The sig-docs/demos which includes all the manifests present in this documentation site. The images are built and tested nightly and upon changes to Automotive Image Builder itself.

  • The sample-images repos which includes a collection of manifests. Note that those images are not regularly tested and while most of them are included in sig-docs/demos there may still be a few additional interesting manifests examples.

Note

AutoSD does not support cross-compilation. To build AArch64 or x86_64 images, you must build on the respective systems. Some options for AArch64 hosting include Raspberry Pi 4 or QEMU on Linux or macOS. For more information, see Getting started on Linux or macOS.

Prerequisites

Procedure

  1. Build a disk image from your manifest:

    $ aib-dev build \
    <my-manifest>.aib.yml \
    <my-image>.qcow2

    The example command demonstrates how to build a qcow2 image for a virtual environment using the most basic options. Additional options are available. You can also build images for specific hardware types.

    Tip

    For production deployments, use aib build to produce a bootc container image instead. Bootc images support over-the-air updates and registry-based distribution. For details, see Building bootc images.

  2. Run the image:

    $ air --nographics <my-image>.qcow2

  3. After the image boots, log in as root using the password password.

  4. Verify that your packaged software is present in your image:

    # rpm -q auto-apps dlt-daemon vsomeip3-routingmanager

Your image is now ready.

Next steps

  • Now that you have built your AutoSD image, you can flash it onto an SD card. For more information, see Provisioning hardware.

Additional resources

© Red Hat