Can't use with persistent storage about consul

[sdelrio]

hello @galindro, I build this as a demostration for the docker scale, I didn't make it for the purpose of persistent storage, because most of the consul cluster I saw was based on independent service for each consul instance.

I don't know much about the internal behaviour of the consul itself, but I think that when you save the persistent data and start a new stack again, the containers could not have the same IP, so perhaps it loose some IP configuration and because that could make a a leader election (perhaps they are waiting for response of a non-existant IP). You could check it writing the IP addresses before stoping the stack and when starting again, and look if they match on the logs for the voter and leader election when starting the 2nd time.

You could also try the placement constraint using a label instead of a node.role == manager, make something like consul == true and add labels to nodes. Then try to remove one label from one node and add it again to see if it joins, then try remove one label, then a remove a 2nd label, and add the two labels again.

[sdelrio]

No answer on the last months so I will close this. Reopen if needed.