You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My desire with this was to have the client's graceful shutdown capability usable from docker commands. Given that docker stop defaults to a 10 second delay before killing the container though, and an ongoing render could take upwards of half an hour to complete, that may simply not be feasible. If you want to take a look, let me know how it goes.
Since this issue was created docker runtime added support for the --init option,
If enabled it just interjects the tini init system, which handles signal handling and process reaping automatically (the latter won't be an issue in sheepit's case most likely) and doesn't interfere with anything else.
Though it would most likely kill the render process immediately.
With the new signal handling in the client, being able to send a ctrl-c via
docker kill
would be a nice feature.The text was updated successfully, but these errors were encountered: