Skip to main content
Version: Developer

Build an install or upgrade command

Overview​

The Kasm Workspaces installer and upgrader accept several dozen flags, and the right set depends on the role, whether the install is offline, and how observability is deployed. This page builds the command for you. Choose the script and role, select the flags you need, fill in values, and copy the result into the install guide's download and extract steps.

Everything on this page runs in your browser. Values you type are never sent anywhere. Passwords you leave empty appear as placeholders in angle brackets.

Prerequisites​

note

The generated command appears directly below the steps and updates as you change the form. It uses long flag names with one flag per line, so it can be pasted into a change ticket or a runbook. Select One line, no line continuations for a single line that pastes cleanly into a terminal. For the meaning of each observability flag, see Observability configuration. For the full upgrade procedure, see Single-server upgrade or Multi-server upgrade.

Detailed steps​

  1. Optionally pick a preset under Start from a preset. Presets mirror the single-server and multi-server installation guides, common observability scenarios, and the 1.20.0 upgrade paths. Hostnames and paths are examples to replace, and passwords are left for you to fill in.
  2. Select Script: install.sh for a new host, upgrade.sh for an existing install.
  3. Select Role. Single-server deployments use all. Multi-server deployments run the wizard once per role.
  4. Select the flags you need in each group and fill in their values. Groups that do not apply to the selected role are hidden. Select Show flags for every role to list them anyway.
  5. Read the Fix before running and Review before running boxes. The first lists flags the selected role requires, marked required in the flag list, and combinations the installer rejects or that cancel each other out, such as --skip-otel together with any observability flag. The second lists choices that lose data or leave a node misconfigured, such as an upgrade of the database role without --backup-logs-file.
  6. Copy the generated command and run it from the directory that holds kasm_release/.
Options
Generated install.sh command
sudo bash kasm_release/install.sh
General14 flags
Accept the End User License Agreement without prompting.
Verbose output.
Installation profile from kasm_release/profiles: noninteractive or hardened.
Port the proxy listens on. The default is 443.
Initial admin@kasm.local password.
Initial user@kasm.local password.
License activation key file to apply during install.
Zone name this server belongs to.
Hostname or IP of the Web App that agents register with and send heartbeats to. On the agent role this is the Web App the agent joins.
Do not start services when the install finishes.
Copy this public SSL certificate into place during install.
Copy this private SSL key into place during install.
Default Workspaces Registry URL.
Connection Proxy cluster size. 0 selects automatic sizing.
Database5 flags
Password of the Kasm database user.
Kasm database user name.
Kasm database name.
Disable SSL on the database connection.
Skip database initialization.
Offline install5 flags
Path to the service images offline tar.gz.
Path to the workspace images offline tar.gz.
Path to the network plugin images offline tar.gz.
Path to the logger plugin images offline tar.gz.
Force dependency installation even during an offline install.
Images6 flags
Seed and download the default Workspaces images.
Use static, version-pinned service images. Recommended for new installs and initial-build upgrades.
Use rolling service images.
Specific tag for service images. Defaults to the build date.
Enable the lossless streaming option.
Skip v4l2loopback installation (webcam passthrough).
Observability6 flags
Do not install the OTel Collector or ClickHouse. Sticky across upgrades until --enable-otel is passed.
Bearer token for inter-collector authentication. Generated on the app or all node when omitted, and required on every remote node.
Use a custom OTLP collector instead of the bundled one.
Forward all telemetry to this OTLP/HTTP endpoint in parallel.
Bearer token for the forward endpoint.
Percent of non-error, non-slow traces kept. The default is 10.
ClickHouse8 flags
Do not install the bundled ClickHouse and configure no external replacement. Telemetry is not stored.
Native-interface DSN of a dedicated or external ClickHouse for the collector.
HTTPS URL of the same ClickHouse for Kasm UI reports and logs. Required together with --clickhouse-endpoint.
ClickHouse database name. The default is kasm_otel.
Writer user name. The default is kasm_otel.
Writer password. Sets the server password on the clickhouse role and the connect password on app.
Read-only user name the API uses for reports and logs. The default is kasm_otel_ro.
Read-only password. Sets the server password on the clickhouse role and the connect password on app.
Retention4 flags
General log retention in days. The default is 30.
Audit log retention in days. The default is 365.
Trace retention in days. The default is 7.
Metrics retention in days. The default is 90.
Checks and dependencies9 flags
Skip the database, API, OTel Collector, and ClickHouse connectivity checks.
Do not check for open ports.
Do not check disk space.
Disable the swapfile check.
Create a swapfile of this many megabytes when none exists.
Do not install the egress network plugin or its dependencies.
Install the stock Rclone plugin without modification.
Enable the EPEL repository for packages missing from the default RHEL repositories.
Continue when optional dependencies fail to install.