supports building snap based and classic preinstalled Ubuntu images.
model assertion uniquely describe the device for which the image is built.
bootloader and if so what kind of bootloader, etc.
with the resulting tree ending up in the prime/ directory.
Show the program's message and exit.
Show the program's version number and exit.
when the ubuntu-image snap command is used.
Extra snaps to install. This is passed through to snap prepare-image.
cloud-config data to be copied to the image.
The snap channel to use.
These are the options for defining the contents of  classic  preinstalled  Ubuntu  images.
Can only be used when the ubuntu-image classic command is used.
must be given for this mode of operation.  Must be a local path.
Project name to be passed on to livecd-rootfs.
Distribution name to be passed on to livecd-rootfs.
Sub-project name to be passed on livecd-rootfs.
Sub-architecture to be passed on to livecd-rootfs.
Extra ppas to install. This is passed through to livecd-rootfs.
generating a disk image file.  These options are useful in this mode of operation.
you to run the internal state machine step by step, and is described in more detail below.
image will be written to the current working directory.
MiB and 'G' for GiB.
sizes, you could use --image-size 0:2G,sdcard:8G,eMMC:4G.
the volume will be used instead.
by the command, if any.
build-time hooks will be located.
a .ubuntu-image.pck file in the working directory.
the working directory after it's downloaded.
of a state machine method, or a number indicating the ordinal of the step.
a state machine method, or a number indicating the ordinal of the step.
there is no previous state.
The following environment variables are recognized by ubuntu-image.
command which prepare-image is called on.
the snap prepare-image subcommand has run will be copied here.
livecd-rootfs through a call to dpkg.
it will attempt to find a matching emulator binary in the current $PATH.
There are a few other environment variables used for building and testing only.
variables depending on the hook being fired.
Includes the absolute path to the rootfs contents.
  Volumes are roughly analogous to disk images.
Records, or any other relevant content.