KUHBS Kuh Build System Qubes OS KUHBS Kuh Build System
English KUHBS Qubes OS website
Menu

Documentation

Upgrading KUHBS Managed VMs

Review repository changes, back up required data, and upgrade KUHBS-managed VMs without rerunning Create-time setup or regenerating launchers.

Update and review the repository before upgrading its KUHBS-managed VMs. A repository update changes the available definition; it does not automatically change existing Qubes OS VMs.

Before upgrading

  1. review the repository update and select the exact commit you intend to trust;
  2. run kuhbs check;
  3. back up the KUHB’s required persistent data; and
  4. read the changed definition and update hooks so you know what the upgrade will do.

Run the upgrade

Use Upgrade on the KUHB card in the graphical interface, or run:

kuhbs upgrade <kuhb-id>

Upgrade updates the managed TemplateVMs and StandaloneVMs and runs explicit update hooks. It does not rerun Create-time setup scripts or regenerate launchers.

Upgrade one KUHB at a time when practical. Keep the visible terminal open, record the exact repository commit and result, then start the affected application and verify its network path, launcher, and required persistent data before upgrading the next KUHB.

If an update changes Create-time setup, generated launchers, or the KUHB topology, review and back up the required data, then use Remove and Create instead. KUHBS has no automatic rollback, so verify the application after every upgrade.

Next: Backing Up KUHBs .