Side-Load Workload Images
Side-load legacy or custom KVM workload images into the packaged STRATUM environment. This is an advanced, unsupported workflow in standard deployments and should not be used casually.
Bring existing KVM images into STRATUM
Side-loading is an advanced compatibility path for legacy or custom KVM images that already exist outside Arsenal. It is not a supported standard/community workflow. Enterprise customers should use it only as part of a STRATUMvisor-supported procedure because direct modification of packaged application content can break assumptions that normal Arsenal workflows protect.
A STRATUM upgrade, container deletion, or reinstall will not preserve files that were added only inside the current application container. In the current release, an enterprise deployment that intentionally needs those changes to survive can commit the modified Docker/Podman container to a new image and tag, then configure stratum-host to use that image tag. Treat that as an advanced Datacenter-as-an-Application workflow, not normal Arsenal administration.
Disk filenames identify the guest disk bus and slot. Keep the image directory name aligned with the template name so STRATUM can associate the files with the intended workload definition.
Commands
Use the filename convention that matches the virtual disk bus expected by the template.
VirtIO Block: virtioa.qcow2, virtiob.qcow2, ...
VirtIO SCSI: sda.qcow2, sdb.qcow2, ...
The letter identifies the disk slot: a is the first disk, b the second, and so on.Procedure
Side Load Workload Image Directory
Copy the existing KVM workload directory into the STRATUM addon image location. Keep the directory name aligned with the template that should expose the image.
Side Load Template Name Matching
Use the expected disk naming convention inside the addon directory and make sure the template name matches the directory. Refresh Arsenal after the files are in place.
The outcome you should see
After Arsenal is refreshed, the side-loaded workload appears under the matching template and can be deployed through System Arsenal.