Disable stack versioning

[Xitee1]

Ask a Question!

Hello,
since I have upgraded from CE to Business edition (using the take-3 offer), there is a versioning for stacks. Each time I modify a stack, a new version gets created. Is there a way to disable this? It is really annoying for me to always copy the data to the new version folder manually. I don't need the versioning.
I could not find any option to disable it. If it cannot get disabled, I sadly have to use the CE version again to overcome these disadvantages.
Main reason for the upgrade was to easily see if the containers are up to date.

Does anyone know something about that?

[Nick-Portainer]

Hey!

Can you please break down the steps for me to reproduce your issue?

Are you creating a Stack, let's say Nginx webpage, adding in the site contents to the data location, but when you make a change your stack is now running in a v2 folder which no loner contains the data you copied in orginally?

My above is just a inital assumption, please let me know :)

[Xitee1]

Yes, that is correct. But I forgot to mention that I use relative paths.
Example:

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

This initially stores the data in /data/compose/1/v1/nginx-proxy-manager.
If I change something in the stack, it is /data/compose/1/v2/nginx-proxy-manager. The data remains in the v1 folder.
With the CE Edition of Portainer there was no v-sub-folder, it was like this: /data/compose/1/nginx-proxy-manager.

[Nick-Portainer]

Thank you for this, I have raised this internally and will get back to you pending internal feedback :)

[Xitee1]

I'm now using absolute paths, so it isn't really a problem to me anymore. Since it annoyed me anyway to search the number-named folders to find the data of my services I moved everything to absolute paths.
However I think it would still be good to prevent that the relative paths changes every time a (small) change to the stack is made.

But thanks for your help 😄

[Nick-Portainer]

Sorry for the delayed response, this bug is tracked internally and we are looking to have it resolved in the next release or so, but can confirm closer to the release date.

But to confirm, we are aware of this issue and have a solution in the pipeline that resolves this in terms of files not moving to the new versioned folder :)

Internal: EE-6190

[rimvy]

The same thing happens for me on Portainer BE 2.19.4. Any fixes for this issue?

[Xitee1]

As I've already mentioned, I'm just using absolute paths now. In the beginning I preferred relative paths but now I actually like to use absolute paths more because I have more control about where the data gets stored.
But in a classic setup without portainer and a docker-compose.yaml file relative paths are of course better for config stuff.

[jorisdonkers]

Same issue here. Portainer BE 2.19.5 .I don't need the stack versioning and i still would like to use relative paths in stacks as in the CE version. I would really love to see a setting to disable this. Using absolute paths feels a bit weird and defeats the purpose of a stack for me.

[Bodo-von-Greif]

Same issue here with nginx-proxy-manager.

Took me much too much time to realize all my nginx-proxy-manager users and configuration where gone due to this issue.
Please definetly create a warning or better a possibility or switch this off!

[rew-ron]

We solved this by using

    volumes:
      - ../data:/data

vs

    volumes:
      - ./data:/data

Notice the double dot on the relative path, ../. Essentially just going one directory up making it behave like Portainer CE while still having the option to use the versioned directories.

[Bodo-von-Greif]

Thanks ron,

guess thats why i ended in a subdirectory disaster with nginx-proxy-manager like:

/data
└── compose
└── 3
├── data
├── letsencrypt
├── v1
├── data
├── letsencrypt
├── v2
├── data
├── letsencrypt
└── v3
├── data
├── letsencrypt

[Nick-Portainer]

Hi all, I have raised this internally regarding updating the stack results in data loss for the container. I have also confirmed this myself testing with NPM. I will reply here with any updates

internal: EE-7093