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

  1. Open the Service.
  2. Go to the Volumes tab.
  3. Define mount paths and volume definitions as the UI allows.
  4. 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

  1. Open the Service β†’ Volumes.
  2. Remove the volume from configuration.
  3. 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