Skip to content

Building an image from a custom manifest

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.

Prerequisites

Procedure

  1. Build the AutoSD image. In this example, specify your manifest file and the qcow2 image format in the build command:

    $ automotive-image-builder build --export qcow2 <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.

  2. Run the image:

    $ automotive-image-runner <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

Additional resources

Flashing the image on an SD card

To install the OS on a hardware device, flash the image onto an SD card.

Prerequisites

Procedure

  • Flash the image onto an SD card:
$ dd if=<my-image>.qcow2 of=<SD card device path> status=progress bs=4M

Important

You must change the value for of=<SD card device path> to match the block device path used in your system, for example /dev/sdb. If required, add -bios /usr/share/OVMF/OVMF_CODE.fd to QEMU command.


© Red Hat