RunPod only persists /workspace, and serverless mounts volumes at /runpod-volume
Shows how to fix runPod only persists /workspace, and serverless mounts volumes at /runpod-volume. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
Never delete a network volume that holds models or projects you still need. Deleting the network volume removes the persisted projects, generated assets, and downloaded models with it, and a volume must be attached at pod creation because it cannot be attached later.
Steps
- Write everything durable under /workspace on pods, and re-check the mount after any pod edit before assuming data loss. Attach the network volume at pod creation, since it cannot be attached later. Never delete a network volume that holds models or projects you still need.
When to use
You are seeing this: Write everything durable under /workspace on pods, and re-check the mount after any pod edit before assuming data loss. Use this skill when you run into "RunPod only persists /workspace, and serverless mounts volumes at /runpod-volume".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Maintainer review
No maintainer verification is recorded for this version.
This records the version a maintainer checked. It does not assert that the version is the latest upstream release.