Linux Server Update Package Procedure
Cyolo servers are updated in one of two ways.
- Virtual appliance. Cyolo publishes Appliance Core and OS updates. Apply them from the Launcher Maintenance tab. The appliance OS image is read-only, so
apt-getanddnfdo not update it. - Linux base installation. The host operating system is updated with the distribution package manager. Use this procedure for an IDAC, Private Gateway, or Connector installed on Ubuntu or RHEL. Update one machine at a time, inside an approved maintenance window of 1 hour for that machine.
Virtual appliance
The appliance lists two Cyolo-managed updates on the Maintenance tab under Appliance Upgrades.
| Update | What it changes | What the appliance does |
|---|---|---|
| Appliance Core | The appliance runtime: the launcher, the console, and the OS manager | Restarts appliance services. The machine keeps running. |
| OS updates | The operating system image | Writes the new image to the inactive partition, switches the bootloader, and reboots. The previous OS stays on the other partition. Configuration and data stay on the data partition. |
The appliance checks for newer versions about every 10 minutes. Each download is checksum-verified before it can be applied.
Automatic updates are on by default. Maintenance windows are enabled, Sunday 02:00–04:00 UTC, and the tab also shows that window in the local timezone. Pending updates apply while a window is open.
An admin can turn automatic updates off. Switch off Enable Maintenance Windows and click Save. Both update types then stay Pending until an admin applies them with Upgrade now.
When both updates are pending, Appliance Core is applied first. The OS update follows, and that step reboots the appliance.
Apply an appliance update
- Open the Cyolo Launcher Web UI and select the Maintenance tab. The tab shows a count when updates are waiting. The header shows the versions that are running now: the deployed component, OS, APPLIANCE, and the tenant.
- Review the two lists on the page:
- Pending Upgrades lists component updates, such as Private Gateway. This list can read No pending upgrades while appliance updates are waiting.
- Appliance Upgrades lists Appliance Core and OS updates. Each row shows the name, version, and status. OS updates also shows a short build id.
In this example, maintenance windows are enabled for Sunday 02:00–04:00 UTC. The line under the days shows that same window in the appliance timezone. The page says Outside maintenance window, so both rows stay Pending: Appliance Core v0.7.0 and OS updates v0.4.0. They apply when the window opens, or when an admin clicks Upgrade now.
- Leave Enable Maintenance Windows on to keep automatic updates. The default window is Sunday 02:00–04:00 UTC. Select other days, change Start (UTC) and End (UTC), or click Add Window, then click Save.
- To turn automatic updates off, switch off Enable Maintenance Windows and click Save.
- To apply the pending updates immediately, click Upgrade now and confirm.
- Appliance Core moves through Applying and Restarting while appliance services restart.
- OS updates move through Applying and Rebooting. The appliance reboots and active sessions are interrupted.
- Upgrade now stays unavailable while an update is already Applying, Restarting, or Rebooting.
- After an update finishes, that row leaves Appliance Upgrades. The header then shows the new OS and APPLIANCE versions.
An OS update reboots the appliance. Apply it in a maintenance window, or when a short outage is acceptable.
The appliance needs outbound access to Cyolo services to download updates. After repeated download failures, retries slow to about once an hour until a download succeeds.
Roll back from the boot menu
On boot, GNU GRUB shows this menu for 5 seconds:
- Cyolo A
- Cyolo B
- Reboot (automatic fallback)
The highlighted entry is the partition the appliance will boot. To roll back, press the up or down arrow until the other Cyolo entry is highlighted, then press Enter. That boots the previous partition.
If you do not choose an entry, the highlighted partition boots.
If the new OS does not start successfully, the appliance tries it three times and then boots the previous partition on its own. A successful start clears that retry count.
Reboot (automatic fallback) restarts the machine and returns to this menu.
Linux base installation
Run this procedure on the host operating system of an IDAC, Private Gateway, or Connector. Work on one machine at a time.
1. Take a system backup
Take a snapshot of the machine in the hypervisor or cloud console, or take a full system backup. Wait until the snapshot finishes before you continue. Restore this snapshot if the machine does not pass the sanity check after reboot.
2. Approve the maintenance window
Get approval for a maintenance window of 1 hour for this machine. Start the package update only after that window is approved.
3. Sanity check
Record the results before you install packages.
Disk usage and free disk
df -hConfirm the root filesystem and the Cyolo data disk have free space for the package download and install.
IDAC, Private Gateway, and Connector
docker ps -aConfirm each component installed on this machine is running. Docker is the supported runtime on RHEL. Podman is not supported.
List every known error before the upgrade: containers that are not running, and errors already open for this machine. Compare this list with the check after reboot.
4. Install operating system packages
Run the commands for the host operating system. The same Ubuntu commands apply to 22.04, 24.04, and 26.04.
Ubuntu 24.04
Refresh the package list:
apt-get updateInstall the updates:
apt-get upgradeReboot:
rebootRHEL 8, 9, and 10
Refresh the package list and show the updates that are available:
dnf check-updatednf check-update exits with status 100 when updates are available. That status means the list was retrieved, and the upgrade can continue.
Install the updates:
dnf upgradeReboot:
reboot5. Sanity check after reboot
Log in after the machine comes back and repeat the sanity check from step 3.
- Run
df -hand confirm disk space is still within the expected range. - Run
docker ps -aand confirm the IDAC, Private Gateway, and Connector on this machine are running. - Compare the error list with the list taken before the upgrade.
When a component is not running, or a new error appears, restore the snapshot from step 1 and report the error before you update the next machine.
Updated about 16 hours ago