Mount a named volume when creating or running a sandbox. The volume name goes before the colon, the guest path after. CLI named mounts are idempotent: if the named volume is missing, microsandbox creates it; if it already exists with compatible settings, microsandbox reuses it.
# Create or reuse a directory-backed named volume, then mount itmsb run --name worker -v app-data:/data python# Create or reuse a disk-backed named volume, then mount itmsb run --name docker-demo \ --mount-named docker-data:/var/lib/docker:kind=disk,size=20G \ docker:dind# Share between sandboxesmsb run --name writer -v shared:/data alpine -- sh -c "echo hello > /data/msg.txt"msb run --name reader -v shared:/data alpine -- cat /data/msg.txt
--mount-named accepts named-volume creation options in the mount option block: kind=dir|disk, size=<size> for disk-backed volumes, and quota=<size> for directory-backed volumes. kind=disk requires size=...; size=... without kind=disk is rejected. If an existing volume has a different kind, capacity, or quota than the requested settings, sandbox creation fails instead of silently changing the volume.
The CLI distinguishes bind mounts from named volumes by looking for a / or . prefix. ./src:/app is a bind mount (host path). myvolume:/data is a named volume. This matches Docker’s convention.
Was this page helpful?
⌘I
Assistant
Responses are generated using AI and may contain mistakes.
