Upgrading Containerized Consoles#

There are two independent things you may need to keep up to date: the Console Server software running on each VM, and the console container images used for sessions.

Upgrading the Console Server software#

To upgrade a Console Server, re-run the installer on that VM as root:

curl -fsSL https://distribution.synergycp.com/scripts/console-server-installer.sh | bash

The installer detects the existing installation and upgrades it in place. Your configuration, certificate, and API key are preserved, so you do not need to re-register the Console Server in SynergyCP. The scp-console-server service is restarted automatically when the upgrade finishes.

Repeat this on each Console Server VM. After upgrading, confirm the Health column on the Console Servers page returns to OK.

Updating console images#

The console container image is what actually runs inside each session. New image versions are published to the console image catalog. To move servers onto a newer image:

On the Console Servers page, use Refresh console image catalog to pull the latest available images and tags.
Re-assign the affected servers’ Launch KVM Action (see Enable Containerized Consoles on servers) and select the newer Console Tag.

Existing sessions keep running on the image they started with; the new image is used the next time a console is launched.

Support for uploading ISOs into a console depends on both SynergyCP 5.5+ and a console image that includes it. If uploads aren’t available after upgrading SynergyCP, refresh the catalog and move your servers onto the latest console image. Note that even when supported, ISO uploads work only for consoles launched by a user account with an SSH key set — admin accounts cannot upload ISOs.