Chapter 3. Embedding applications for offline use

Procedure

1. Render the manifests, extract all of the container image references, and translate the application image to blueprint container sources by running the following command:

   $ oc kustomize ~/manifests | grep "image:" | grep -oE '[^ ]+$' | while read line; do echo -e "[[containers]]\nsource = \"${line}\"\n"; done >><my_blueprint>.toml

   Copy to Clipboard Toggle word wrap

2. Push the updated blueprint to Image Builder by running the following command:

   $ sudo composer-cli blueprints push <my_blueprint>.toml

   Copy to Clipboard Toggle word wrap

3. If your workload containers are located in a private repository, you must provide Image Builder with the necessary pull secrets:

   1. Set the auth_file_path in the [containers] section of the osbuilder worker configuration in the /etc/osbuild-worker/osbuild-worker.toml file to point to the pull secret.

   2. If needed, create a directory and file for the pull secret, for example:

      Example directory and file

      [containers]
      auth_file_path = "/<path>/pull-secret.json" 

      1

      Copy to Clipboard Toggle word wrap

      1

      Use the custom location previously set for copying and retrieving images.

4. Build the container image by running the following command:

   $ sudo composer-cli compose start-ostree <my_blueprint> edge-commit

   Copy to Clipboard Toggle word wrap
5. Proceed with your preferred rpm-ostree image flow, such as waiting for the build to complete, exporting the image and integrating it into your rpm-ostree repository or creating a bootable ISO.