veri volumes group manages persistent named storage in your workspace. A training job reads a volume either as one file connected with datasets.from_volume (downloaded at job start) or, coming soon, as a whole-volume read-only mount at /mnt/<name> through the job-level volume field. Conceptual overview lives in the Volumes guide.
Commands
Create a volume
^[a-zA-Z0-9][a-zA-Z0-9_-]{0,127}$. Re-running with the same name returns the existing volume: no error.
Upload files
For a single file:/<filename>. Override with --to:
List + inspect
Delete
--yes to skip the prompt in scripts:
Pipe-friendly output
--quiet strips formatting and emits just the relevant id:
--format json|jsonl|csv swaps the table renderer for machine-readable output, and the progress bar on uploads is suppressed.
Common workflows
Migrate from a local directory
Inspect failed uploads
Ifvolumes upload-dir aborts mid-batch, files that completed are already on the volume. Re-running the same command uploads every file again; S3 PUT is idempotent on the same key, so nothing is duplicated.
Next steps
Volumes overview
What volumes are and how they are billed.
REST API
/v1/volumes endpoints + multipart upload protocol.
