Chris Tawfik

If you do it the way I described in the README, if the first container would be created new, it would behave just as any other container started later. Because...

Hi @Franselbaer, I saw similar problems with the cluster discovery itself. Sometimes, if you do scale-out and scale-in repeatedly, the new nodes wont find existing ones. Or the cluster might...

I have been looking into this for quite some time. But I cant figure out a way to do it. With mode global more than one instance would start at...

I am happy that you found a pretty fine solution for this problem. Will keep it in mind if I need to do such a setup one time. Thanks, Chris

If you just want to have a place, where the data is stored for backup reasons, this is a way to go. But if one tasks dies, it is restarted...

I am not quite sure, if this isnt a default behavior. Means, that if you would hard kill a classic Cluster Node, it would result in the same error/problem when...

I got the stuff with the configs wrong in my last posting. In a non-persistent setup you dont have any problems, since /etc/mysql and /var/lib/mysql are within the container and...

Hi @yaakov-berkovitch, I have an idea, but it has nothing to do with the healtcheck. I was playing around and found that compose version 3 does not work with swarm...

No problem. I could rebuild a Portus/Registry stack with official and current versions of Portus and DockerRegistry. But thanks a lot for your work and effort. It made my setup...