Lost settings and configuration of containers after update / redeployment

[woll-knaeuel]

Ask a Question!

I just wonder if I have a missconfiguration or doing something wrong when updating my stacks/containers within portainer.
Not every time but from time to time I lost all my settings and configuration of the updated containers. The first time I was shocked but than I realized that the following happens:
during the update / redeployment process a new directory (probably version if I am interpreting the folder name correctly) is beeing created in the /data/compose/xx/ folder
Example:
befor the update I have one directory an all settings and data beeing stored in
/data/compose/11/v1
after the update I have a new folder next to "v1" which is named "v2" (next time "v3" ...)
/data/compose/11/v2
I manually have to copy the data (settings) from v1 to v2 and everything is back to normal, otherwise the container behaves like a clean and fresh untouched installation / setup.
Is this ment to be like this or am I doing something wrong during the update process or have a configuration flaw?
Is this related to this discussion https://github.com/orgs/portainer/discussions/9761?