Build Results
The image type is selected with the image attribute of the
<preferences> element, see <preferences>. After a
successful kiwi-ng system build or kiwi-ng system create, the target
directory contains the image and further files. Their names follow the
pattern:
<image-name>.<arch>-<version>.<extension>
<image-name> is the name attribute of the <image> element,
<arch> the architecture of the build, <version> the <version>
element of the preferences, and <extension>
depends on the image type. kiwi-ng result list lists the results of
the last build in a target directory.
Image Types
The examples below use the image name kiwi-test-image-some, the
architecture x86_64 and the version 1.15.3.
|
Image |
Result files |
|---|---|---|
|
A disk image for virtual machines, clouds or bare metal, which
can resize itself to the disk it is deployed on. Optionally with
an install ISO ( |
|
|
A hybrid live ISO image, which boots from CD/DVD or a USB stick without touching the storage of the system. See Build an ISO Hybrid Live Image. |
|
|
A container image for Docker, loadable with |
|
|
A container image in the format of the Open Container Initiative. |
|
|
A container image for the Windows Subsystem for Linux 2.4.4 or later, a gzip-compressed tar archive. See Build a WSL Container Image. |
|
|
A container image for the Windows Subsystem for Linux, the former
format replaced by |
|
|
A root filesystem image with a kernel and an initrd, packed into
one archive, for custom deployments such as network boot. |
|
|
An initrd-based image in the |
|
|
The root tree in a filesystem image of the given type. |
|
|
The root tree in an xz-compressed tar archive. |
|
|
The root tree in a cpio archive. |
|
Further Result Files
Every build also creates the following files:
<image-name>.<arch>-<version>.packagesThe packages of the image, sorted, one per line in the format
name|epoch|version|release|arch|disturl|license. The fields are based on RPM metadata. Fields which other package managers do not provide are set toNone. Compare the files of two builds to track package changes.<image-name>.<arch>-<version>.verifiedThe result of the package verification of
rpmordpkgagainst the package database, in the RPM verification format. It shows the state of all packages before the first boot of the image.
Bundling Results
kiwi-ng result bundle copies the files needed for a release from the
target directory into a bundle directory, see kiwi-ng result bundle.
It appends the given identifier to the version in the file names:
$ kiwi-ng result bundle --target-dir /path/to/build_result \
--bundle-dir /path/to/release_result --id release_identifier
For example, kiwi-test-image-some.x86_64-1.15.3.iso
is bundled as
kiwi-test-image-some.x86_64-1.15.3-release_identifier.iso.
For other file names, set the bundle_format attribute of the type
element, or use the option --bundle-format, which takes precedence:
<type image="..." bundle_format="%N-%v-%I"/>
The format is the base name of the bundled files and supports the following placeholders:
Placeholder |
Value |
|---|---|
|
The |
|
The profiles used for the build, joined with |
|
The architecture of the build, as reported by Python’s
|
|
The identifier of the |
|
The |
|
The major, minor and patch number of the |
|
The |