Single Server Installation - Kasm 1.14.0 Documentation
Single Server Installation - Kasm 1.14.0 Documentation
Single Server Installation - Kasm 1.14.0 Documentation
Installation Guide
Please review the System Requirements before beginning.
cd /tmp
curl -O https://kasm-static-content.s3.amazonaws.com/kasm_release_1.14.0.3a7abb.tar.gz
tar -xf kasm_release_1.14.0.3a7abb.tar.gz
sudo bash kasm_release/install.sh
Note
If you have an Activation Key it can be passed to the installation script and activation will be completed on your behalf as part of
the install. Create a file for the Activation Key e.g. activation_key.txt and paste in the Activation Key you received in you
confirmation email. When running the install.sh use the parameter -a or --activation-key-file so your command might look
something like this sudo bash kasm_release/install.sh -a activation_key.txt . This will not work with an offline air-gapped install, as
Kasm Workspaces must contact an activation server to complete licensing your installation. In a multi server install this option only
applies to the database role.
Note
If you would like to run the Web Application on a different port pass the -L flag when calling the installer. e.g sudo bash
kasm_release/install.sh -L 8443
I t ll Vid T t i l
Install Video Tutorial
This video walks through installing Kasm Workspaces on a single system.
Slim images
Using the install flag --slim-images will download and use slim Alpine based service containers. These images are smaller and more
simplified yet retain the same functionality. These images do not have the same broad compatibility as the default Ubuntu containers.
Known incompatibility:
OS x86_64 aarch64
Centos Stream 8 X X
AlmaLinux 8 X X
Rocky Linux 8 X X
Gamepad passthrough is currently not functional. If enabled for a group, workspaces will not launch.
Note
This only effects the service containers running the Kasm Workspaces application, this flag has no effect on end user facing
Workspaces.
Install troubleshooting
The install.sh script creates a log file as it runs, this file is removed upon completion of a successful installation. However, if something does
go wrong the logfile will be available from the directory the install.sh script was executed from in the format kasm_install_${TIMESTAMP}.log.
This file will be important for diagnosing the error that caused the installation to fail and will be requested when submitting a support ticket
with Kasm Technologies.