Skip to main content

System updates

xcon OS updates the whole operating system as one signed image, using two system slots (A and B).

How an update runs​

  1. In the web console, open System Update and click Check for updates. The box fetches a signed manifest from the update channel and verifies its Ed25519 signature — it trusts the signature, not the transport.
  2. If a newer version is offered, its release notes are shown. Click Download & install.
  3. The new image is downloaded (checked against its SHA-256), written to the passive slot, and the boot flag is armed to try it once.
  4. The box reboots into the new version as a one-shot trial. The agent commits the new slot only after a health gate — core services (management agent, firewall, SSH, networking) are up and the system is not in a failed state. If the trial does not pass, the box automatically reboots and falls back to the previous slot — a bad update can't permanently capture the box. A boot that hangs entirely is caught by a hardware watchdog, which reboots it into the same fallback. Either way, recovery is automatic.

A full-screen progress dialog follows the update through the reboot and reloads the console when the box returns.

Rollback​

System Rollback points the boot flag back at the other slot, which still holds the previous version, untouched. The card names the exact version you'll return to.

What an update never touches​

Updates replace only the system image. Your data, installed apps, credentials, hostname, and configuration live on the data partition and are carried across unchanged — and across a rollback too.

From the CLI​

sudo xconctl update check
sudo xconctl update install --reboot
sudo xconctl update rollback --reboot