-
Bug description Expected behavior Portainer Logs Steps to reproduce the issue:
Technical details:
Additional context |
Beta Was this translation helpful? Give feedback.
Replies: 9 comments 2 replies
-
I wanted to follow up on this request. Am I understanding that you want to create a compose stack in Swarm? Can you post your compose code that I can test with? Thanks! |
Beta Was this translation helpful? Give feedback.
-
@tamarahenson
|
Beta Was this translation helpful? Give feedback.
-
I wanted to follow up on this request. The reason we do not provide the option to create compose in Swarm is due that compose is designed for Docker Standalone and not Docker Swarm. Thanks! |
Beta Was this translation helpful? Give feedback.
-
@tamarahenson |
Beta Was this translation helpful? Give feedback.
-
You can use the API:
Thanks! |
Beta Was this translation helpful? Give feedback.
-
@volschin I support your idea. @tamarahenson I have the same needs; Please consider this proposal. |
Beta Was this translation helpful? Give feedback.
-
This feature would be useful because overlay networks don't work when swarm mode is not enabled (no VNI provided error) and I would like to use overlay networks with my compose-created containers. |
Beta Was this translation helpful? Give feedback.
-
Small work around for those having existing compose stacks. Empty one of those stacks to only have one service without volumes, networks, container names and such conflicting things. Then use the "Stack duplication / migration" function with duplication option to create another one with the stack name you want. And you have your new compose stack you can fill with your new input in the second step. |
Beta Was this translation helpful? Give feedback.
-
I still have the problem, is there a solution to this that doesn't require having a stack already in compose mode? My preferred solution would be, as the author suggested, to simply have the option to choose between compose and swarm when creating the stack. |
Beta Was this translation helpful? Give feedback.
Small work around for those having existing compose stacks. Empty one of those stacks to only have one service without volumes, networks, container names and such conflicting things. Then use the "Stack duplication / migration" function with duplication option to create another one with the stack name you want.
And you have your new compose stack you can fill with your new input in the second step.