Kill container on app start fail about uwsgi-nginx-docker HOT 4 CLOSED

If you are using an orchestrator like Kubernetes, you can add some liveness probe that will restart the container if either nginx or uwsgi is not working.

In any case, you can override the supervisor configuration file in your image to fit your needs!

I've been myself thinking of an even more extreme solution for some time now: have a dedicated nginx container and a dedicated uwsgi container. This way, it is atomic. But I haven't done it because... this image simply works for our use case and is easily debuggable.

from uwsgi-nginx-docker.

Made the simple required steps to make image crash on app fail:
https://gist.github.com/ReallyLiri/f833510d350b242ff89b9b76fdf21ea5

from uwsgi-nginx-docker.

Thanks for the discussion everyone! And thanks for the example @ReallyLiri.

I implemented it here: #110

The only caveat is that currently, Supervisor terminates "cleanly", with a 0 return code. I imagine it would be ideal for it to terminate with a non-zero return code, but it doesn't seem to be supported by Supervisor. I imagine it could be possible to "hack" around and make something (like the event handler maybe?) exit with some unexpected result, to make Supervisor take it as an error and exit with an error code. But that seems quite hacky, and probably not trivial to implement.

But for this specific issue, I hope that PR and the latest version of the image would handle it.

from uwsgi-nginx-docker.

Assuming the original issue was solved, it will be automatically closed now. But feel free to add more comments or create new issues.

from uwsgi-nginx-docker.