Skip to main content
Version: 1.19.0 (latest)

Rolling Image Management

Rolling Image Management lets you control how and when Kasm images receive updates by choosing rolling or static tags. Rolling tags pull the latest builds on startup to keep security fixes and patches current, while static tags lock to a specific release for change control. Kasm provides a rolling utility to manage rolling images that Kasm uses to run.

The default behavior of the Kasm installer is to use rolling images. To install Kasm using static images, pass in the -f or --use-static-images arguments during the installation process.

sudo bash kasm_release/install.sh -f

The Kasm installer also accepts a specific dated rolling image tag to use during the initial install. To specify a dated rolling image, pass in the -F or --use-tag arguments and the dated rolling image tag desired during the installation process. If the -F or --use-tag arguments are used without specifying a dated rolling tag, the installer defaults to the dated rolling tag matching its own build date.

sudo bash kasm_release/install.sh -F 1.19.0-rolling-2026-05-01

Example of rolling images, static images, and dated rolling images:

  • Rolling Image: 1.19.0-rolling (updated frequently)
  • Static Image: 1.19.0 (Will not be updated)
  • Dated Rolling Image: 1.19.0-rolling-2026-05-01 (Will not be updated)

Rolling Utility​

The Rolling Utility will help manage the rolling images used by Kasm. The utility contains the following capabilities:

For multi-server installation, run the rolling utility on each server.

Note

This utility will only apply to the core Kasm services.

  • API
  • Agent
  • Manager
  • Proxy
  • RDP Gateways
  • Postgres

Rollback​

This capability will roll back the image that Kasm uses to run. Since the rolling image is updated frequently, in the event that the latest rolling image is causing a problem with Kasm, you can roll back to the version immediately previous to the current image. The utility will switch the image tag and keep it on the previous tag until you use the switch to latest feature.

sudo /opt/kasm/bin/utils/rolling_util -r

In addition to rolling back to the immediate previous version, you can specify a tag version to use during rollback.

sudo /opt/kasm/bin/utils/rolling_util -r 1.19.0-rolling-2026-05-01

This is helpful if you want to roll back to a specific and earlier version of the image. To find what version is available, please visit Docker Hub and search for any Kasm component (i.e. api). Docker Hub will list all available tags.

Note

If specifying a tag, please only use tags that contain the current version of Kasm. Do not use an older version (e.g. specifying 1.18.0 tags when Kasm 1.19.0 is installed)

After using this capability, please restart Kasm.

sudo systemctl restart kasm
Rollback Limitation

If you switch to the latest rolling tag (i.e. with -l) from a dated rolling tag (i.e. installed with -F) and then attempt to rollback to the previous dated tag using -r without a specified value, verify the resulting tags in your docker compose file to ensure that the images have switched to using a SHA. It is possible that the latest rolling tag and your dated rolling tag were pointing to the same image SHA, which would cause the rolling util to leave the rolling tag on the images. If this is the case, you will need to rollback again and provide the dated rolling tag from before. E.g. -r 1.19.0-rolling-2026-05-01

Check Current Image​

This capability will output the creation date of the image currently being used by Kasm, as well as the creation date of the previously used image. This information is helpful when troubleshooting potential problems. If contacting the Kasm team for assistance, please include this information.

sudo /opt/kasm/bin/utils/rolling_util -d

Switch to latest​

During a rollback, Kasm pins the rollback version, effectively making Kasm behave as if using static images. This capability will switch Kasm back to using the latest rolling image.

sudo /opt/kasm/bin/utils/rolling_util -l

After using this capability, please restart Kasm.

sudo systemctl restart kasm

Update Rolling Tag​

This capability will update the Rolling Ledger to track the current and previous running image.

Note

The Rolling Ledger will be updated automatically after every restart. Normally, you will not need to use this capability manually.

sudo /opt/kasm/bin/utils/rolling_util -u

Clean Up Ledger​

This capability will remove any unused images' information that was being tracked in the Rolling Ledger.

Note

Since image information can be useful in troubleshooting, please do not use this capability without being directed by the Kasm Team.

sudo /opt/kasm/bin/utils/rolling_util -c