Virt-launcher image configuration values

The worker.vmRender.launcherImage value specifies the virt-launcher container image that the Red Hat Edge Manager control plane uses when rendering VM applications for edge devices. You can configure this value to use the Red Hat downstream virt-launcher image instead of the default upstream image.

Table 1. Virt-launcher configuration parameters
Parameter Type Default Description

worker.vmRender.launcherImage

string

not set

The virt-launcher container image reference. When not set, the worker uses a default community image that is not supported by Red Hat. Set this value to the Red Hat virt-launcher image for production deployments.

worker.vmRender.passtWorkarounds

boolean

false

Enables startup patches for known networking issues, such as guest network instability, in older virt-launcher passt builds. Enable this only if your configured virt-launcher image requires the workaround.

Example configuration values
Copy link

The following example configures the Red Hat Edge Manager control plane to use the Red Hat downstream virt-launcher image:

worker:
  vmRender:
    launcherImage: registry.redhat.io/container-native-virtualization/virt-launcher-rhel9:v4.22-1784929080
Note

Both Red Hat Enterprise Linux 9 and Red Hat Enterprise Linux 10 currently use the same Red Hat virt-launcher image (virt-launcher-rhel9).

Network passthrough workaround

The worker.vmRender.passtWorkarounds value is false by default. Enable it only if your configured virt-launcher image requires this networking workaround. Check your virt-launcher image’s release notes, or contact Red Hat support, to confirm whether your image needs it:

worker:
  vmRender:
    launcherImage: <older_virt_launcher_image_reference>
    passtWorkarounds: true

Applying the configuration

Add the worker.vmRender.launcherImage value to your Helm chart configuration during installation or upgrade, or to your standalone Red Hat Enterprise Linux configuration file.

Red Hat OpenShift Container Platform

For a new installation, include the values in the helm install command:

$ helm install <release_name> <chart> -f <values_file>.yaml

For an existing installation, apply the values during a Helm upgrade:

$ helm upgrade --reset-then-reuse-values <release_name> <chart> -f <values_file>.yaml

Replace <values_file> with the path to your Helm values file that contains the worker.vmRender.launcherImage configuration.

Red Hat Enterprise Linux with Podman Quadlets

Edit /etc/flightctl/service-config.yaml directly:

worker:
  vmRender:
    launcherImage: registry.redhat.io/container-native-virtualization/virt-launcher-rhel9:v4.22-1784929080

Restart the worker so it reloads the configuration:

$ sudo systemctl restart flightctl-worker.service
Important

When you use the Red Hat virt-launcher image, every target edge device must have pull credentials for registry.redhat.io configured at /root/.config/containers/auth.json. Without pull credentials, the agent cannot pull the virt-launcher image and the VM application fails to start.

Checking the current value
Copy link

To find the worker.vmRender.launcherImage value currently configured on your Red Hat Edge Manager control plane, check the location for your deployment platform.

For Red Hat OpenShift Container Platform deployments, view the Helm release values:

$ helm get values <release_name> -n <namespace>

For standalone Red Hat Enterprise Linux deployments, check the configuration file on the Red Hat Edge Manager server:

$ grep -A2 launcherImage /etc/flightctl/service-config.yaml

Disconnected environment configuration

In air-gapped or disconnected environments, mirror the Red Hat virt-launcher image to an internal registry and set the launcherImage value to the internal registry path:

worker:
  vmRender:
    launcherImage: <internal_registry>/container-native-virtualization/virt-launcher-rhel9:v4.22-1784929080

Replace <internal_registry> with the hostname and port of your internal registry, such as registry.internal.example.com:5000.