Skip to content

Update from code changes: dashboard sandbox volume management #428

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mintlify wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Update from code changes: dashboard sandbox volume management #428

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b7725a3
docs: note dashboard management for sandbox volumes
mintlify[bot] Jul 22, 2026
b10041f
docs: note sandbox-volumes is a reserved add-on name
mintlify[bot] Jul 22, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions sandboxes/overview.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -92,6 +92,17 @@ Volumes provide persistent storage that can be mounted into sandboxes at launch.
- [TypeScript Sandbox SDK volumes](/sandbox/sdk/typescript/volumes)
- [Sandbox CLI volume commands](/sandboxes/cli#porter-sandbox-volume)

### Manage volumes from the dashboard

Every cluster with sandboxes enabled has a **Sandbox file storage** card in the **Add-ons** page, backed by a managed `sandbox-volumes` persistent-disk add-on that Porter creates and owns. The name is reserved — creating your own add-on named `sandbox-volumes` will fail with a validation error. Open the card to see:

- **Overview** — the shared EFS disk backing sandbox volumes, with its created date and metered storage used.
- **Volumes** — the cluster's volumes, with name, phase, attached sandboxes, and created date. Filter by name or phase, click a row to open the volume detail page, and delete idle volumes from there.

Volumes attached to a running sandbox cannot be deleted; terminate the sandbox first, then delete the volume once it detaches.

When you mount the `sandbox-volumes` disk into an app service, the dashboard shows a confirmation dialog reminding you that volume contents are written by sandboxed workloads and must be treated as untrusted input. See [accessing volume data from apps](/sandbox/sdk/python/volumes#access-volume-data-from-apps) for the full pattern.

## Next steps

- [Sandboxes Getting Started](/sandboxes/getting-started)
Expand Down