Replies: 10 comments 9 replies
-
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 :) |
Beta Was this translation helpful? Give feedback.
-
Yes, that is correct. But I forgot to mention that I use relative paths. volumes:
- ./nginx-proxy-manager/data:/data This initially stores the data in |
Beta Was this translation helpful? Give feedback.
-
The same thing happens for me on Portainer BE 2.19.4. Any fixes for this issue? |
Beta Was this translation helpful? Give feedback.
-
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. |
Beta Was this translation helpful? Give feedback.
-
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. |
Beta Was this translation helpful? Give feedback.
-
We solved this by using volumes:
- ../data:/data vs volumes:
- ./data:/data Notice the double dot on the relative path, |
Beta Was this translation helpful? Give feedback.
-
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
|
Beta Was this translation helpful? Give feedback.
-
Any news about this? It is really frustrating |
Beta Was this translation helpful? Give feedback.
-
Upgrading from community to business edition caused a ton of my containers to fail. This was the final straw to migrate away from this app. |
Beta Was this translation helpful? Give feedback.
-
This has been marked as resolved as of 2.21 - Leaving open for confirmation for 30 days |
Beta Was this translation helpful? Give feedback.
-
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?
Beta Was this translation helpful? Give feedback.
All reactions