Skip to main content
The 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

Names must match ^[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:
The remote path defaults to /<filename>. Override with --to:
Files larger than 5 GiB are uploaded with S3 multipart automatically. A progress bar shows transfer rate, ETA, and total transferred. For a directory:
Up to 8 files transfer concurrently. The progress bar reports cumulative bytes across all files. A per-file failure aborts the batch. You can safely re-run: an upload to the same path replaces the file.

List + inspect

List files inside a volume:

Delete

Prompts for the volume name as confirmation and shows the file count + total bytes that will be deleted. Pass --yes to skip the prompt in scripts:
The DB row is dropped immediately; the S3 prefix is reaped by a background reconciler within ~60 seconds. There is no undo. Delete a single file inside a volume without removing the volume itself:

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

If volumes 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.