Building Base Images
A base image is simply an image that has no parent. Atomic reactor can be
used to build base images by using Koji's image build functionality via
Add Filesystem Plugin
FROMinstruction in Dockerfile. If value is "koji/image-build", this plugin proceeds. Otherwise, no further processing is performed and the plugin quits.
Parses the image build configuration from
image-build.confwhich is used to create an image build task in Koji. A different name for the image build configuration file can be specified by using a tag in the
FROMinstruction. For example,
FROM koji/image-build:custom.confwill load configuration from
Downloads produced filesystem tarball from Koji and uses docker's
importto load it as an image. The
FROMinstruction in Dockerfile is modified to use the ID of the newly imported image.
Build proceeds as usual.
from_task_id plugin parameter to use the tarball from an existing
Image Build Configuration
The image build configuration file is used to specify how the filesystem will
The syntax for this file is equivalent to the syntax used when in the config
file used for Koji's CLI client image build subcommand:
koji image-build --config config
For convenience, defaults are provided to minimize the size of the configuration
file. See the
DEFAULT_IMAGE_BUILD_CONF variable in
source for all defaults.
ksurlitem is by default dynamically mapped to the current branch and commit;
targetitem is by default set to the koji target parameter and should be omitted from the config file. If explicitly set in the file, the default value is overridden.
It's important to note that currently in the
create_docker_metadata parameter must be set to
False. Setting this
True, will alter the format of the tarball produced by Koji which
add_filesystem plugin does not support.