Chapter 3. Building an application package

Procedure

1. Prepare your application configuration: Create the configuration file required for your chosen format (for example, application.container). Ensure that you define any persistent data requirements by using volumes within these configuration files.

   Note

   To ensure Quadlet services restart automatically after a device reboot, include an [Install] section in your .container file (for example, WantedBy=default.target).

2. Create the OCI artifact: Use the podman artifact add command to package your configuration.

   For a single file, run:

   podman artifact add quay.io/<your_org>/<your_image_name>:v1 application.container

   For multiple files, bundle them into a compressed archive first. Create the archive:

   tar czf app-bundle.tar.gz application.container config.json

   Add the archive to the artifact:

   podman artifact add quay.io/<your_org>/<your_image_name>:v1 app-bundle.tar.gz

   Note

   Podman version 5.5 or later is required for the artifact command. The Red Hat Edge Manager agent automatically extracts .tar.gz, .tar, and .tgz archives into the application directory on the edge device.

3. Push the artifact to your registry: Upload the packaged artifact to your OCI-compatible registry:

   podman artifact push quay.io/<your_org>/<your_image_name>:v1

Procedure

1. Update the device specification: Reference the OCI artifact in the image field of your device resource. You can define and override runtime configurations such as environment variables, ports, and volumes in the device specification.

   spec:
     applications:
       - name: sensor-collector
         appType: quadlet
         image: quay.io/myorg/sensor-collector:v1
         envVars:
           SENSOR_ID: "unit-42"
         volumes:
           - name: model-data
             image:
               reference: quay.io/myorg/sensor-models:latest
               pullPolicy: IfNotPresent
             reclaimPolicy: Retain
         runAs: flightctl

Procedure

1. Package and push the chart:

   helm package .

   Push the chart to your registry:

   helm push <chart_package.tgz> oci://quay.io/<your_org>/<your_chart_name>

2. Configure the device specification: To customize a Helm application, provide configuration overrides directly in the Device resource by using the values or valuesFiles fields.

   applications:
     - name: wordpress
       appType: helm
       image: quay.io/myorg/my-chart:1.0.0
       values:
         replicaCount: 2