Skip to main content
Attach existing volumes when you create a sandbox.

Mount at Sandbox Creation

Use the SDK, CLI or REST API to mount volumes at sandbox creation.
Raw mounts payload:

CLI --mount Formats

Use repeated --mount flags.
Examples:
Examples:

Mount Object Fields

string
required
Volume ID (UUID).
string
default:"rw"
Access mode: rw or ro.

Naming Rules

  • Mount path must be absolute and below /.
  • Mount path cannot be /.
  • Mount path must already be normalized.
  • Mount path cannot target protected system locations such as /etc, /usr, /proc, /dev, /root, /run, or /sys.
  • Duplicate mount targets are rejected.
  • Volume must exist and belong to your team.

Launch Behavior

At launch, Hyperbrowser resolves each mount to a team-owned volume, then provisions runtime mount instructions with scoped access. If mount resolution fails, sandbox creation fails.
Mounts are currently configured at sandbox launch. Updating mounts on an already running sandbox is not supported

Next Step