Concepts
Workspaces come with temporary storage that disappears when stopped. To keep your data, you must use a persistent volume.- Workspace volume: Dedicated, high-performance (NVMe) persistent volume for a single workspace.
- Best for: Code, virtualenvs (pip/conda), per-workspace data.
- Mount path:
/root($HOME) (fixed)
- Shared volume: Team-shared POSIX-compatible filesystem backed by S3 object storage.
- Best for: Datasets, checkpoints, large artifacts to share across the team.
- Recommended path:
/shared
- Temporary volume: Default ephemeral storage included in every workspace.
- Note: Data is wiped when the workspace is stopped.
A shared volume behaves like a network file share with RWX (read-write-many) semantics across workspaces.
A workspace volume behaves like a PVC-backed disk with RWO (read-write-once) semantics for a single workspace.
Terminology mapping
| Concept | Our term | Kubernetes (typical) | Other products | Notes |
|---|---|---|---|---|
| Shared (team) | Shared volume | PV/PVC on NFS/SMB/EFS (RWX) | Shared volume (provider-specific); some use commit/reload semantics | Network file share, multi-workspace |
| Per-workspace | Workspace volume | PV/PVC (RWO) | Provider volume attached per workload (for example, pod/function) | Dedicated disk-like, single workspace |
| Ephemeral | Temporary volume | emptyDir | Local workspace/container filesystem | Deleted on stop/terminate |
Typical workflows
- Create and Manage: Create a shared volume to store your data.
- Share: Share datasets and models across workspaces using shared volumes.
- Persist: Keep per-workspace state in workspace volumes.