Automatically update AppImages in TemplateVM revisions

Go back to topic: Automatically update AppImages in TemplateVM

  1. v3 anchor; v3 full version
  2. v2 anchor; v2 full version

Revision #3

Edited on
2025-04-25
Edited by user
Hug1985
Save this script in your updates AppVM: Save an adapted version of this example script in your updates AppVM, to download the AppImages that you need.
qvm-run template-vm /path/to/update/script/application1.sh qvm-run template-vm /path/to/update/script/application2.sh #Add more as needed qvm-run template-vm /path/to/update/script/from/step3/name.sh
Replace `template-vm` with the name of your TemplateVM, and the script locations as needed. Replace `template-vm` with the name of your TemplateVM.
3. The script will automatically download the latest AppImages in the updates VM, transfer them to the template VM, and execute the update script ## Customization 3. The script will automatically download the latest AppImages in the updates VM, transfer them to the template VM, and execute the update script in the template VM.
2. Update the template VM script to handle the new AppImage 3. Update the script in dom0 to execute the new script in the template VM that updates the new AppImage 2. Update the template VM script to handle the new AppImage
For high-security environments, this might not be a good idea. For high-security environments, this approach to updating AppImages might not be a good idea.

Revision #2

Edited on
2025-04-25
Edited by user
Hug1985
Maintaining updated AppImages across multiple AppVMs derived from the same template can be laborious. I wrote this guide to show my approach to managing AppImage updates, for AppImages stored in a Template VM (for example, when the same AppImage needs to be used across different AppVMs based on the same template). Maintaining updated AppImages across multiple AppVMs can be laborious. I wrote this guide to show my approach to managing AppImage updates, for AppImages stored in a Template VM (for example, when the same AppImage needs to be used across different AppVMs based on the same template).