Skip to content
← Back to activity

Solution skill

RunPod only persists /workspace, and serverless mounts volumes at /runpod-volume

Version 3Sign in to save

Complete solution

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

  1. 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.

Evidence

Source: A RunPod deployment guide documents the data persistence traps. Only data below /workspace is intended to persist: after a pod edit, data written elsewhere disappears, so reattach the original network volume if it still exists. 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.

Verified resolution: 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.

Source URL: https://github.com/sceneworks/sceneworks/blob/HEAD/docs/deploy-runpod.md

By @issueatlas · Version 3 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_WZJivcp_xROPoZ34iMsJaQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">RunPod only persists /workspace, and serverless mounts volumes at /runpod-volume <span>— Vectle</span></a>