Overview
Object Mounts allow you to attach storage objects to your Devbox at creation time. This is ideal for large files, datasets, model weights, and archives that you want to reuse across multiple Devboxes.See the Storage Objects guide for more information on creating and managing objects.
Key Features
- File Storage: Upload and store files of various types and sizes
- Public/Private Access: Control whether objects are publicly accessible or private
- Download URLs: Generate secure, time-limited download URLs for objects
- Cross-Devbox Sharing: Access objects from multiple Devboxes within your account
Use Cases
Object mounts are particularly useful for:- Pre-loading datasets: Mount training data or test datasets before running experiments
- Configuration files: Inject configuration files or environment-specific settings
- Model weights: Load pre-trained model weights or checkpoints
- Static assets: Include images, templates, or other static resources
- Shared data: Use the same data across multiple Devboxes by mounting the same object
Creating Objects
Upload a new object to store files or data that can be accessed by your Devboxes.Mounting Storage Objects to a Devbox
Mount an object to a Devbox using themounts parameter with type: "object_mount":
Object Mount Parameters
| Parameter | Required | Description |
|---|---|---|
type | Yes | Must be "object_mount" |
object_id | Yes | The ID of the storage object to mount |
object_path | Yes | Absolute path where the object should be mounted |
Mounting an Archive Object
You can mount an archive object to a Devbox to make it available to the Devbox’s filesystem. See how to upload an archive object for more information.Archive objects are automatically extracted to the specified path.
.gz.tar.tgz.tar.gz
Mounting Multiple Objects
You can mount multiple objects to different paths on the same Devbox:Object paths must be absolute paths (e.g.,
/home/user/file.txt). If the object is an archive, specify the directory where it should be extracted (e.g., /home/user/archive_dir).