A new /data/compose/3/v<x> directory is created with a vanilla database.sqlite whenever i pull new releases about nginx-proxy-manager

[remcoros]

That is an issue (or feature) of portainer when you create a stack and use relative paths for your volumes. Whenever the stack/compose content is updated, it creates a new version and you end up with a whole new 'v##' folder which is used for relative volume mappings. I switched to using absolute paths for the volumes because of this.

[Bodo-von-Greif]

Hi remcoros,

at the end i suspected portainer for doing this. Thanks a lot for confirming this!
Also i see there is a version switch at the right upper corner when you edit the stack.
How did you manage to switch to absolute paths?

Best,
Bodo

[remcoros]

don't use ./data:/data, but point to a full path on your host system like this:

    volumes:
      - /data/nginx-proxy-manager/data:/data

[Bodo-von-Greif]

Thats a way better answer than KI:

Gemini: how do i prevent portainer from creating new versions of stack direcories?

There isn't a direct way to disable stack versioning in Portainer currently. This feature was a point of discussion among users on the Portainer GitHub Discussions https://github.com/orgs/portainer/discussions/10415.

Here are two options to consider:

1. Use Portainer CE: If stack versioning is a major inconvenience, you can switch to the Portainer Community Edition (CE). Unlike the Business Edition, the CE version doesn't automatically create new versions for your stacks.

2. Manage Data Volumes Manually: Even with stack versioning, your data volumes (folders containing persistent data) typically remain in the original location. You can manage these volumes manually and copy them over to the new version directory if needed. This approach requires some manual intervention but avoids creating new data copies every time.

thanks again!