Looking at Php8.2 update - dockerised version where it says, when doing a docker version upgrade, to delete the volume mounted at /var/www/eramba.
Does eramba actually make modifications to /var/www/eramba aside from /var/ww/eramba/app/upgrade/data and /var/www/eramba/app/upgrade/logs?
I ask for this reason: I am deploying the containers to kubernetes. Volume mounts in k8s have slightly different behavior than docker compose. With docker, a mounted volume does not fully hide was is in the image. It allows for a kinda-of change-on-write semantics.
But k8s fully hides what was previously at the mount point. So mounting volumes at
/var/www/eramba
/var/ww/eramba/app/upgrade/data
/var/www/eramba/app/upgrade/logs
results the application no longer existing in the container.
Eramba starts and runs just fine with just the data/ and logs/ mounted. But its not clear to me whether when the pod restarts if changes out side of data/ and logs/ will be lost.
Given the the link above says to delete the volume mounted /var/www/eramba it seems that any changes outside of data/ and logs/ is not required to be maintained. But if that is the case, why have the volume at /var/www/eramba at all?
I was wondering the same thing on my K8s testing environment, I’m running it without volume /var/www/eramba and had no issues so far but I also would like to know the answer.
We currently have limited experience with running Eramba on Kubernetes (K8s), but we would appreciate your assistance in creating a simple deployment guide once you’ve successfully set it up.
Regarding your question, the reason for deleting the Eramba folder, as mentioned in the instructions you provided, is due to the need to implement changes at the Docker level. It is not possible to update PHP solely through the user interface.
During runtime, modifications are made only to the data and logs folders. Changes to the Eramba folder are applied only when performing updates, which involve altering PHP files and other core components.
One challenge to be aware of is that each time Eramba is redeployed, the correct version of the image must be used. These images are not publicly accessible and must be manually downloaded from our download portal. This could lead to discrepancies between the application version and the database version.
