Describe why it is important and where it will be useful
Most if not all apps put their persistent data in this volume so it would be nice to override it so the local data can be used/the data can be kept even after the ex-app is removed completely (with data).
Describe your proposed solution
Check for the mount mapping in the docker container, if it tries to bind the exact same path as the persistent volume, do not try to mount the persistent volume and use this one.
A sample ex-app register command to mount a volume:
occ app_api:app:register APP_ID harp_proxy_docker --wait-finish --mount /path/in/local/storage/persistent_storage_my_app:/nc_app_APP_ID_data
Describe alternatives you've considered, if relevant
No response
Additional context
No response
Describe why it is important and where it will be useful
Most if not all apps put their persistent data in this volume so it would be nice to override it so the local data can be used/the data can be kept even after the ex-app is removed completely (with data).
Describe your proposed solution
Check for the mount mapping in the docker container, if it tries to bind the exact same path as the persistent volume, do not try to mount the persistent volume and use this one.
A sample ex-app register command to mount a volume:
Describe alternatives you've considered, if relevant
No response
Additional context
No response