You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[Kasm](https://www.kasmweb.com/?utm_campaign=LinuxServer&utm_source=listing) Workspaces is a docker container streaming platform for delivering browser-based access to desktops, applications, and web services. Kasm uses devops-enabled Containerized Desktop Infrastructure (CDI) to create on-demand, disposable, docker containers that are accessible via web browser. Example use-cases include Remote Browser Isolation (RBI), Data Loss Prevention (DLP), Desktop as a Service (DaaS), Secure Remote Access Services (RAS), and Open Source Intelligence (OSINT) collections.
41
40
@@ -71,25 +70,27 @@ Access the installation wizard at https://`your ip`:3000 and follow the instruct
71
70
72
71
Currently Synology systems are not supported due to them blocking CPU scheduling in their Kernel.
73
72
74
-
### Updating KASM
73
+
### Upgrading KASM
75
74
76
-
In order to update kasm, first make sure you are using the latest docker image, and then perform the in app update in the admin panel. Docker image update and recreation of container alone won't update kasm.
75
+
In order to upgrade Kasm, first make sure you are using the latest docker image, and then perform the in app update from the installation wizard. Docker image update and recreation of container alone won't upgrade Kasm.
76
+
77
+
Following the upgrade, you will need to update any workspace image tags to match the new version.
77
78
78
79
### GPU Support
79
80
80
-
During installation an option will be presented to force all Workspace containers to mount in and use a specific GPU. If using an NVIDIA GPU you will need to pass `-e NVIDIA_VISIBLE_DEVICES=all` or `--gpus all` and have the [NVIDIA Container Runtime](https://github.com/NVIDIA/nvidia-container-runtime) installed on the host. Also if using NVIDIA, Kasm Workspaces has [native NVIDIA support](https://www.kasmweb.com/docs/latest/how_to/gpu.html) so you can optionally opt to simply use that instead of he manual override during installation.
81
+
During installation an option will be presented to force all Workspace containers to mount in and use a specific GPU. If using an NVIDIA GPU you will need to pass `-e NVIDIA_VISIBLE_DEVICES=all` or `--gpus all` and have the [NVIDIA Container Toolkit](https://github.com/NVIDIA/nvidia-container-toolkit) installed on the host. Also if using NVIDIA, Kasm Workspaces has [native NVIDIA support](https://docs.kasm.com/docs/latest/how-to/gpu/index.html) so you can optionally opt to simply use that instead of he manual override during installation.
81
82
82
83
### Gamepad support
83
84
84
-
In order to properly create virtual Gamepads you will need to mount from your host `/dev/input` and `/run/udev/data`. Please see [HERE](https://www.kasmweb.com/docs/develop/guide/gamepad_passthrough.html) for instructions on enabling gamepad support.
85
+
In order to properly create virtual Gamepads you will need to mount from your host `/dev/input` and `/run/udev/data`. Please see [HERE](https://docs.kasm.com/docs/latest/guide/gamepad_passthrough/index.html) for instructions on enabling gamepad support.
85
86
86
87
### Persistant profiles
87
88
88
-
In order to use persistant profiles in Workspaces you will need to mount in a folder to use from your host to `/profiles`. From there when configuring a workspace you can set the `Persistant Profile Path` to IE `/profiles/ubuntu-focal/{username}/`, more infomation can be found [HERE](https://www.kasmweb.com/docs/latest/how_to/persistent_profiles.html).
89
+
In order to use persistant profiles in Workspaces you will need to mount in a folder to use from your host to `/profiles`. From there when configuring a workspace you can set the `Persistant Profile Path` to IE `/profiles/ubuntu-focal/{username}/`, more infomation can be found [HERE](https://docs.kasm.com/docs/latest/guide/persistent_data/persistent_profiles).
89
90
90
91
### Reverse proxy
91
92
92
-
A sample for [SWAG](https://github.com/linuxserver/docker-swag) can be found [here](https://raw.githubusercontent.com/linuxserver/reverse-proxy-confs/master/kasm.subdomain.conf.sample). Post installation you will need to modify the "Proxy Port" setting under the default zone to 0 as outlined [here](https://www.kasmweb.com/docs/latest/how_to/reverse_proxy.html#update-zones) to launch Workspaces sessions.
93
+
A sample for [SWAG](https://github.com/linuxserver/docker-swag) can be found [here](https://raw.githubusercontent.com/linuxserver/reverse-proxy-confs/master/kasm.subdomain.conf.sample). Post installation you will need to modify the "Proxy Port" setting under the default zone to 0 as outlined [here](https://docs.kasm.com/docs/latest/how-to/reverse_proxy/index.html#update-zones) to launch Workspaces sessions.
93
94
94
95
### Strict reverse proxies
95
96
@@ -127,6 +128,7 @@ services:
127
128
ports:
128
129
- 3000:3000
129
130
- 443:443
131
+
stop_grace_period: "90s"#optional
130
132
restart: unless-stopped
131
133
```
132
134
@@ -147,6 +149,7 @@ docker run -d \
147
149
-v /path/to/kasm/profiles:/profiles `#optional` \
148
150
-v /dev/input:/dev/input `#optional` \
149
151
-v /run/udev/data:/run/udev/data `#optional` \
152
+
--stop-timeout="90s" `#optional` \
150
153
--restart unless-stopped \
151
154
lscr.io/linuxserver/kasm:latest
152
155
```
@@ -167,6 +170,7 @@ Containers are configured using parameters passed at runtime (such as those abov
167
170
|`-v /profiles`| Optionally specify a path for persistent profile storage. |
168
171
|`-v /dev/input`| Optional for gamepad support. |
169
172
|`-v /run/udev/data`| Optional for gamepad support. |
173
+
|`--stop-timeout=`| Increase container shutdown delay to give Kasm services time to stop cleanly. |
170
174
|`--security-opt apparmor=rootlesskit`| Some hosts require this on top of privileged for namespacing to work properly inside the DinD layer. |
171
175
172
176
## Environment variables from files (Docker secrets)
@@ -313,6 +317,7 @@ Once registered you can define the dockerfile to use with `-f Dockerfile.aarch64
313
317
314
318
## Versions
315
319
320
+
***16.04.26:** - Update for 1.18.1 release. Use rolling service images. Bump docker to v29.
316
321
***13.11.25:** - Pin docker to v28 to avoid API deprecation issues.
0 commit comments