Persistent Data

By default, Kasm Workspaces spins up containerized sessions that are ephemeral in nature. However, some use cases require that certain data or configurations persist between sessions. There are two main ways to achieve this: Persistent Profiles and Volume Mappings.

Persistent Profiles automate the process of mounting a host directory into the Workspace as the users home directory. These are analogous to Roaming Profiles found in other platforms. When configured, users may select whether to use their persistent profile when launching a session, disable it (making the session ephemeral) it, reset the profile - (clearing the contents and starting a fresh profile).

Volume Mappings are a more generic feature that can be used to map host-level directories into the session. They may also be used to share folders across multiple users/workspaces and thus are more appropriate to simulate an organizational share. Volume mapping can be configured at a group level or individual Workspace level.

Please review the documentation links below to get a detailed explanation of each type and how to configure them.

Persistent Data Documentation:

• Persistent Profiles
  • Adding a persistent profile to a Workspace
  • Limiting group access to persistent profiles
  • Utilize a persistent profile with creating a Kasm
  • Video Example
• Volume Mapping
  • Configuration Example
  • User Tokens
  • Volume Mapping Configuration options
  • Configure Volume Mapping at a Group Level
  • Video Example
• Host Configuration Guides
  • Using NFS
  • File Persmissions and Isolation