vers resize

​

Synopsis

vers resize --size <mib>                   # Resize HEAD
vers resize <vm-id|alias> --size <mib>     # Resize specific VM
vers resize --size 4096 --format json

​

Options

​

Examples

​

Grow HEAD to 4 GiB

vers resize --size 4096

​

Grow a specific VM

vers resize my-db-vm --size 8192

​

Script-friendly

vers resize vm-abc123 --size 8192 --format json | jq '.new_size_mib'

​

How it works

​

Common reasons to resize

• A build or install is about to write more than the default fs_size_vm_mib.
• You branched a VM that filled its disk and need headroom on the branch.
• You’re materializing a large dataset (database dump, container image layers) for testing.

​

Common Patterns

​

Grow before a big install

vers resize --size 8192
vers execute -- apt-get install -y heavy-package

​

Check then grow

CURRENT=$(vers info my-vm --format json | jq -r .resources.fs_size_mib)
echo "current: $CURRENT MiB"
vers resize my-vm --size $(( CURRENT * 2 ))

​

Verify inside the VM

vers resize --size 4096
vers execute -- df -h /

​

See also

• vers run — set initial --fs-size-vm when creating a VM
• vers info — inspect current resources including disk size
• vers branch — branches inherit the parent’s disk size