Volumes and persistent storage
Attach persistent volumes to App and Docker Services; mount states and deletion behavior.
Written By Zoro
Last updated 3 days ago
Volumes keep data on disk across Deployments and restarts for Services that support them.
Attach volumes
- Open the Service.
- Go to the Volumes tab.
- Define mount paths and volume definitions as the UI allows.
- Save and Deploy / Redeploy if required.
Mount states
- Mounted: the Service can read and write the volume at the configured path.
- Not mounted: configuration exists but the volume is not attached; the Service cannot access that data path.
Remove volumes
- Open the Service β Volumes.
- Remove the volume from configuration.
- Save and redeploy if prompted.
Removing a volume from the Service stops the app from using that mount; data may remain on the Worker Node host until you reclaim disk separately.
Limitations
Environment variables and volumes for database-type Services are constrained compared with App and Docker Services; follow in-product hints. If something is disabled, use the Service type the UI recommends.
Related
- Service settings (environment variables)
- Docker services
- Deployment issues (when mounts fail at deploy time)