Replies: 1 comment
-
|
FYI, if you are referring to the blog_db service on Swarm1, by using a Docker overlay network your containers and services can communicate with each other across all the nodes of your swarm. I.e wordpress and the db don't have to be on the same host |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Is your feature request related to a problem? Please describe.
I'm trying to set up wordpress with a persistent volume and it's not behaving. So I dropped back to the original stack and now it's not finding the plugins and images I originally uploaded, which are on Swarm1 in the image below.
https://www.screencast.com/t/9MHfKx1K
Describe the solution you'd like
It would be great if I could drag and drop the wordpress container from Swarm3 to Swarm1 and get a popup message that says "do you want to constrain this service to this node (node.hostname) or to a manager/worker (node.role)?" You would then update the service and redeploy.
Beta Was this translation helpful? Give feedback.
All reactions