Current Answer: Update CasaOS Through the UI or the Official Update Script
The 2024 community post points to an external upgrade/downgrade tutorial, but the current CasaOS project itself documents the supported update paths. Use Settings โ Update, or run the official update script from SSH/direct terminal:
curl -fsSL https://get.casaos.io/update | sudo bashThe CasaOS source repository is the authoritative project reference.
Do Not Treat Downgrade as the Mirror Image of Upgrade
The current CasaOS README documents updating to the latest release; it does not document a universal supported downgrade command. Downgrading can cross database, app-management and configuration migrations that were designed to move forward.
Use CasaOS release history to identify the exact version and changes rather than piping an old community command blindly.
Back Up Configuration and App Data Before Version Changes
CasaOS itself is only part of the server. Docker volumes, databases and user files are the expensive state. Record app mappings and make a verified copy before a forced upgrade or rollback attempt.
If the long-term goal is moving to the newer Zima platform, the ZimaOS installation recovery is safer than mixing CasaOS rollback experiments with production data.
Use a Snapshot When CasaOS Runs in a VM
For lab environments, a VM snapshot before the upgrade gives you a much cleaner rollback boundary than downgrading package-by-package after the fact. A snapshot captures the system state the old version actually expected.
Separate CasaOS Maintenance From ZimaOS Maintenance
CasaOS and ZimaOS are different products with different release and recovery models. Do not use CasaOS update scripts on ZimaOS. For a current home-server platform comparison, the ZimaBoard 2 platform provides the current Zima ecosystem context.
