You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
hello, is there any way to re-bind a stack's compose file (via file editing or web-ui)? I noticed at some point one of my stacks went to limited configurability for some reason, but i checked the portainer data volume and it still has its compose file stored in "(volume root)/compose/79", if its not possible without editing the .db file and potentially causing more issues, then can i remove the stack (and connected containers) and re-create it while keeping the same named volume?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Ask a Question!
hello, is there any way to re-bind a stack's compose file (via file editing or web-ui)? I noticed at some point one of my stacks went to limited configurability for some reason, but i checked the portainer data volume and it still has its compose file stored in "(volume root)/compose/79", if its not possible without editing the .db file and potentially causing more issues, then can i remove the stack (and connected containers) and re-create it while keeping the same named volume?
Beta Was this translation helpful? Give feedback.
All reactions