Configure persistent volumes

Use persistent volumes for application files that must be stored outside the container's writable layer. Configure paths during creation or add them later in the application’s Volumes tab.

Add mount pathsCopy Anchor Link

1. In Create resource, find Persistent volume mount paths under Runtime settings.
2. Enter one absolute container path per line, for example:

/app/data
/app/uploads

3. Complete the creation form and deploy the application.
4. Verify that the application can read and write the mounted paths. Check its logs for filesystem permission errors.

Each path receives a dedicated named volume scoped to this resource. The paths are locations inside the container, not directories on the deployment host.

LimitsCopy Anchor Link

• A container can have up to 10 unique mount paths.
• Each path can contain up to 512 characters and must be an absolute non-root path.
• Host bind mounts and volumes shared between resources are not supported by this form.
• Database resources do not expose the Volumes tab or a mount-path editor. Their data volumes are managed by the database service.
• Volumes supports adding dedicated volumes and changing their mount paths for applications without Docker Compose. Imported volumes and host mounts are read-only.
• This editor does not delete volumes, attach shared volumes, or manage backups.

Persistent storage is not a backup. Export important application data before replacing or deleting a resource; do not depend on a deleted resource's storage remaining accessible.

Manage an existing applicationCopy Anchor Link

1. Open Container Engine, select your application and open Volumes.
2. Review the volume names and Mount path values. You need container_engine.instances.read to view them and container_engine.instances.update to save changes.
3. Under Add volume, enter an absolute container path such as /data and select Save. To change an existing dedicated volume, select Edit, change its path and select Save.
4. Redeploy the application using its existing deployment action. Saving volume settings does not restart the application or apply mounts to the running container.

Changing a mount path keeps the same named volume and its data. It does not move files from the container’s writable layer into that volume. A volume mounted over a directory can hide files previously visible at that path; update your application configuration and back up important data before redeploying.

The limit is ten persistent volumes per application. You can edit existing paths at the limit. Changes are unavailable while a resource operation is in progress. Compose-managed mounts must be changed through their deployment configuration.

TroubleshootingCopy Anchor Link

• Could not load volumes: select Refresh. If the error continues, contact support with the resource ID and displayed error.
• Could not confirm the volume save: refresh first. A failed response does not necessarily mean the configuration was not saved. Check the list before retrying the unchanged draft.
• This volume changed: refresh and select Edit again to use its current path.
• This mount path is already in use: choose another path or edit the existing volume. File mounts can also reserve a path.