Mount a volume through v2
POST /v2/sandboxes accepts spec.volumes, a list of at most one {volume, path} entry naming a volume of the same project by its ID (vol_...). The volume is mounted read-write at its path before the sandbox's phase is running; a volume that is still being created is waited for. The sandbox writes the volume alone: while it holds it, no other sandbox mounts it, and it cannot be forked. The API key needs volumes:attach, and must be able to read the volume: without volumes:attach the request returns 403, and a volume the key cannot read, or that does not exist, returns 400. volumes is set when the sandbox is created and cannot be changed. Each path must be absolute, outside /proc, /sys and /dev, and neither at nor inside a file share's path; otherwise the request returns 400.
Same day.
- Desktops: capture the screen with POST /v2/desktops/{id}:screenshot and drive it with POST /v2/desktops/{id}:actA screenshot returns the whole screen as base64, as png or jpeg (set quality, 1 to 100), with its width and height.
- Apps, Functions and Containers: volumes are mountedA version whose spec.volumes names a volume now mounts it in each copy before its process starts.