-
-
Notifications
You must be signed in to change notification settings - Fork 218
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
**Feature Request** Restart Stack instead of just container #128
Comments
Hi, sorry for my intrusion, I think this can be linked to #49, I also have this problem and until not long ago the solution worked, since I reinstalled everything something is not working, during startup it goes into an endless loop, I think the entrypoint proposed is "old" J |
Ok, like I said I tried to modify the entrypoint with the modification of #49 but is not working, I don't know how to debug it, I leave it here hoping someone can fix it
|
Thank you @smarthome-enthusiast I'll take a look, I've some problem too about compose with more than one services |
@Jorman managed to get the new script working fine with the latest version. For those looking for a solution, thank @baroka in #49 (comment) for his awesome entrypoint script. Steps:
@willfarrell Firstly, thanks for the fantastic docker. Any chance of integrating this? |
Hi @smarthome-enthusiast yes seems to work but with some small adjustments to do.
In my case this's working without specify labels for master/slave, but I'm under testing now, seems that from compose 2.20, more or less, this functionality is active, but you know, for me the best will be if this method will be integrated inside the docker-autoheal |
It would be really great if we could restart the entire stack instead of just the containers. Perhaps we could include a label on the containers, like "autoheal.restart.stack=true", so that when a container is detected as unhealthy, we can stop and restart the entire stack.
The text was updated successfully, but these errors were encountered: