Disks

Disks are persistent block storage volumes that live independently of any VM. Attach one to a VM at an absolute path, and the data survives suspend, resume, and even destroying the VM. A disk lives in one region and attaches to one VM at a time. Once mounted, it’s owned by the VM’s login user. Disks are durable but not backed up. Removing a disk deletes all of its data, permanently.

Lifecycle

State	Billed?	Notes
`CREATING`	No	Provisioning, usually seconds
`READY`	Yes	Attachable, whether attached or not
`ERRORED`	No	Provisioning failed. `disks get` shows why; `disks rm` to clean up.

Create a disk

$ machine0 disks new data --size 50 --region us-west

Attach at VM creation

machine0 new dev1 --attach disk:data path:/data

Attach to a running VM

$ machine0 disks attach data dev1 --path /data

Detach it again with machine0 disks detach data.

See your disks

$ machine0 disks ls
┌───────────────────────────────────────────────────┐
│ Name    Status    Size     Region     Attached To │
│ data    READY     50 GB    us-west    dev1        │
└───────────────────────────────────────────────────┘

Limits

10 disks per account, 5 per VM
10–16384 GB per disk
A disk attaches only to VMs in its own region
Mount paths must be absolute and can’t nest inside one another
Attaching to a running VM requires a managed SSH key
Not yet supported on GPU sizes or NixOS VMs

Billing

~$0.1667/GB/month, billed hourly while the disk is READY — attached or not. See Pricing.

Commands

See CLI reference.

Introduction

Examples

Platform

Reference

Lifecycle

Create a disk

Attach at VM creation

Attach to a running VM

See your disks

Limits

Billing

Commands

​Lifecycle

​Create a disk

​Attach at VM creation

​Attach to a running VM

​See your disks

​Limits

​Billing

​Commands

Lifecycle

Create a disk

Attach at VM creation

Attach to a running VM

See your disks

Limits

Billing

Commands