atomic-reactor(1)

📦 version 4.21.0, in fedora 43, fedora 44

atomic-reactor 💅✨

okay bestie, gather round, because this is the atomic-reactor(1) manual page from the General Commands Manual and it's literally the whole vibe. it builds images. it's iconic. let's go 🎀

✨ SYNOPSIS ✨

atomic-reactor [-h] [-q | -v | -V] {build,create-build-image,inside-build} ...

🦋 OPTIONS 🦋

  • {build,create-build-image,inside-build} — the commands, bestie. pick your fighter 💖
  • -h, --help — shows this help message and dips out
  • -q, --quiet — shhh mode
  • -v, --verbose — say EVERYTHING mode
  • -V, --version — shows the program's version number and exits, periodt

👑 COMMANDS 👑

COMMANDS — atomic-reactor [OPTIONS] build

okay so this one is the main character: it lets you build images. rn you can build images from a git repo, a local path, or a json file with the full build specification. and there are several methods for doing the actual build: inside a build container using docker from the host, inside a build container using a new instance of docker, or within the current environment. choose your adventure 🧚

  • -h, --help — show this help message and exit

COMMANDS — atomic-reactor [OPTIONS] build git

atomic-reactor [OPTIONS] build git
  • -h, --help — show this help message and exit
  • --image IMAGE — name under which the image will be accessible
  • --uri URI — URI of the git repo
  • --df-path SOURCE__DOCKERFILE_PATH — path to Dockerfile within git repo (default is ./)
  • --source-registry REGISTRY — registry to pull base image from
  • --source-registry-insecure — allow connecting to source registry over plain http (living dangerously, no cap 🙈)
  • --target-registries [REGISTRY [REGISTRY ...]] — list of registries to push image to
  • --target-registries-insecure — allow connecting to target registries over plain http
  • --dont-pull-base-image — don't pull or update base image specified in dockerfile
  • --build-image BUILD_IMAGE — name of build image to use (build image type has to match method)
  • --load-plugin [PLUGIN_FILE [PLUGIN_FILE ...]] — list of files where plugins live
  • --method {hostdocker,privileged,here} — choose method for building image: 'hostdocker' mounts socket inside privileged container to use docker from host, 'privileged' runs separate docker instance inside privileged container and 'here' executes build in current environment
  • --commit SOURCE__PROVIDER_PARAMS__GIT_COMMIT — checkout this commit (default is master)

COMMANDS — atomic-reactor [OPTIONS] build json

atomic-reactor [OPTIONS] build json
  • -h, --help — show this help message and exit
  • --build-image BUILD_IMAGE — name of build image to use (build image type has to match method)
  • --load-plugin [PLUGIN_FILE [PLUGIN_FILE ...]] — list of files where plugins live
  • --method {hostdocker,privileged,here} — choose method for building image: 'hostdocker' mounts socket inside privileged container to use docker from host, 'privileged' runs separate docker instance inside privileged container and 'here' executes build in current environment
  • --substitute [SUBSTITUTE [SUBSTITUTE ...]] — provide substitutions for json in form "foo.bar=spam"

COMMANDS — atomic-reactor [OPTIONS] build path

atomic-reactor [OPTIONS] build path
  • -h, --help — show this help message and exit
  • --image IMAGE — name under which the image will be accessible
  • --uri URI — URI of the directory with source (e.g. "file:///foo/bar") or path (e.g. "/foo/bar"); path can be relative
  • --df-path SOURCE__DOCKERFILE_PATH — path to Dockerfile within given directory (default is ./)
  • --source-registry REGISTRY — registry to pull base image from
  • --source-registry-insecure — allow connecting to source registry over plain http
  • --target-registries [REGISTRY [REGISTRY ...]] — list of registries to push image to
  • --target-registries-insecure — allow connecting to target registries over plain http
  • --dont-pull-base-image — don't pull or update base image specified in dockerfile
  • --build-image BUILD_IMAGE — name of build image to use (build image type has to match method)
  • --load-plugin [PLUGIN_FILE [PLUGIN_FILE ...]] — list of files where plugins live
  • --method {hostdocker,privileged,here} — choose method for building image: 'hostdocker' mounts socket inside privileged container to use docker from host, 'privileged' runs separate docker instance inside privileged container and 'here' executes build in current environment

COMMANDS — atomic-reactor [OPTIONS] create-build-image

atomic-reactor [OPTIONS] create-build-image

create build image 💅 Atomic Reactor installs itself inside and is capable of building images within this image. self-sufficient queen behavior, honestly.

  • -h, --help — show this help message and exit
  • --reactor-latest — put latest Atomic Reactor inside (from public git)
  • --reactor-remote-git REACTOR_REMOTE_GIT — URL to git repo with Atomic Reactor (has to contain setup.py)
  • --reactor-local-path REACTOR_LOCAL_PATH — path to directory with Atomic Reactor (has to contain setup.py)
  • --reactor-tarball-path REACTOR_TARBALL_PATH — path to distribution tarball with Atomic Reactor
  • --use-cache — use cache to build image (may be faster, but not up to date — highkey a tradeoff bestie)

COMMANDS — atomic-reactor [OPTIONS] inside-build

atomic-reactor [OPTIONS] inside-build

we do expect we are inside container, therefore we'll read build configuration from json at '/run/share/build.json' and when the build is done, results are written in that dir so Atomic Reactor from host may read those. it's giving passing notes in class 📝

  • -h, --help — show this help message and exit
  • --input INPUT — input plugin name (determined automatically unless given)
  • --input-arg INPUT_ARG — argument for input plugin (in form of 'key=value'), see input plugins to know what arguments they accept (can be specified multiple times)
  • --dont-pull-base-image — don't pull or update base image specified in dockerfile
  • --substitute SUBSTITUTE — substitute values in build json (key=value, or plugin_type.plugin_name.key=value)

🌸 AUTHORS 🌸

the icons who made this happen, no cap:

  • Jiri Popelka <jpopelka@redhat.com>
  • Martin Milata <mmilata@redhat.com>
  • Slavek Kabrda <slavek@redhat.com>
  • Tim Waugh <twaugh@redhat.com>
  • Tomas Tomecek <ttomecek@redhat.com>
and that's the whole page bestie 💖 this one's dated 2016-12-14 and it lives in the General Commands Manual as atomic-reactor(1). go build something cute 🫶✨
📦 where this page comes from