Skip to main content
Use the baseten volume commands to publish new versions, manage tags and expiration, and roll back deployments. For how versions, tags, and references work, see Volumes.

​
Publish a new version

Each push seals a new version. Pass --tag to move a tag to it; only the chunks that changed upload:
List the volume’s versions, newest first, and check where a tag points:
To serve the new version from a deployment that pins a digest, set source in bdn.mounts to the new version’s reference and redeploy. A push fails if another push to the same volume is in progress; run it again.

​
Manage tags

Create or move prod to an existing version without uploading its files again:
The stat output identifies the version the tag now selects. The previous version remains available by digest. Delete a tag without deleting its version:
The volume’s tags no longer include prod. Other tags and digest references still work. You can also set or delete head, which selects the default version for file reads and new deployment mounts. Both operations require confirmation. Deleting head prevents these operations from selecting a default version until you set it again. For options, see tag set and tag delete.

​
Set tag expiration

Set an expiration time for a temporary tag, such as nightly:
Choose a future RFC 3339 timestamp with a UTC offset, no more than 10 years ahead. The volume’s tags show the expiration time. Expiring a tag removes the tag, not its version. To clear the tag’s expiration time, set it again without --expires-at:
The tag no longer has an expiration time. Expiration of its version or volume still removes it. The head tag can’t expire or point at an expiring version.

​
Set volume expiration

Schedule expiration to delete every live version and remove every tag in a volume. The volume then disappears from listings. Move deployments to another volume before this deadline so new replicas can still start. Set a future RFC 3339 timestamp with a UTC offset, no more than 10 years ahead, and confirm the operation when prompted:
Check the expiration time in the stat output. To cancel scheduled expiration, clear it before the deadline:
Clearing expiration after the volume has expired doesn’t restore its contents. Restore individual versions within their recovery window. For command options, see baseten volume update.

​
Roll back a deployment

To roll back a deployment pinned to a digest, find the earlier version with baseten volume versions, set source in bdn.mounts to that version’s reference, and redeploy. You can also move a tag to the earlier version with baseten volume tag set. Moving a tag doesn’t change running replicas; see how deployments resolve tags.

​
Inspect and download data

Download a version or a directory in it:
Download selected files into an existing directory:
For large transfers, tune concurrency and memory using the push and pull options:
For all download options, including path filtering and restarting partial downloads, see baseten volume pull.

​
Delete and restore a version

baseten volume rm deletes one version selected by digest, or every version of a volume with --recursive:
A deleted version stays restorable for 7 days. List deleted versions with --include-tombstoned, and restore one by its full digest:
Restoring a version doesn’t restore its tags. Point deployments at the restored version’s digest, or recreate tags with baseten volume tag set.
Deleting a version that a deployment mounts doesn’t stop its running replicas, but new replicas, including scale-ups, fail to start. Move every deployment to another version before you delete one.

​
Mount paths

Each entry in bdn.mounts mounts one volume read-only at path. BDN rejects a mount path that:
  • Isn’t absolute, is /, or contains ...
  • Is a system root: /bin, /dev, /etc, /lib, /lib64, /proc, /run, /sbin, /sys, /tmp, /usr, or /var. You can mount at a subdirectory such as /usr/share/models unless it overlaps a runtime path.
  • Is in a tree Baseten reserves: /app, /bdn, /bptr, /cache, /control, /probe-bin, /scratch, or /secrets.
  • Overlaps a path the model container uses, such as /dev/shm, /etc/ssl/certs, /root/.cache/huggingface, /usr/bin, or /usr/local/bin.
  • Repeats another mount’s path or a weights mount_location.
Use a path under /mnt, such as /mnt/data.

​
Namespaces Baseten manages

Baseten stores platform data, such as startup caches, container images, and snapshots, in volumes under your organization. You may see namespaces such as caches, images, and snapshots in baseten volume ls. These namespaces are read-only and Baseten manages their lifecycle, so you can’t create, push, or delete volumes under them. For volume mount errors and replica startup failures, see BDN volume troubleshooting.