RDC CloudContainer Engine
Configure persistent volumes
Specify container paths backed by dedicated named volumes during creation.
Use persistent volumes for application files that must be stored outside the container's writable layer. Configure the paths before the first deployment.
Add mount paths
- In Create resource, find Persistent volume mount paths under Runtime settings.
- Enter one absolute container path per line, for example:
/app/data
/app/uploads- Complete the creation form and deploy the application.
- 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.
Limits
- 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.
- The current Console does not provide a post-creation volume editor.
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.