Prerequisites
Run locally. Back up data you need and record the volume ID returned by the list command. Volume mutations require a stopped workspace.
Grow a volume
The size is in MiB. Verify the mounted filesystem size from inside the workspace and confirm the application can still read its data. Do not assume shrinking is supported.
Remove a volume
Removing a volume destroys its data. A workspace root-disk snapshot is not a backup of that volume.
Stop the workspace, remove the volume from the app’s manifest, and then remove the volume by ID:
Update applications that used the mount before starting them. If the volume remains declared in rig.yaml, a later deployment can attempt to create or attach storage again. See storage recovery for backup boundaries.