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
I am wondering if its possible to forward signal from crontab`s job to dumb-init ?
Seems that crontab will always run, no matter of exit codes of its jobs.
What can I do is that instead of exit 1 I will create file and do and Healthcheck in Dockerfile to monitor this file. Unfortunatelly this will mark container as unhealty, but will not exit dumb-init process.
For dumb-init to exit, you'd either need to send it an uncatchable "terminate" signal (i.e. SIGKILL) or have its immediate child die (cron in your case). The uncatchable signal thing won't really work if it's PID 1 though.
The options I'd probably consider are:
Killing the cron process (either in your HEALTHCHECK or when your script fails)
Having some process above cron in the process tree that knows to watch for the file and exits when it appears; when it exits, dumb-init would exit
I am wondering if its possible to forward signal from crontab`s job to dumb-init ?
Seems that crontab will always run, no matter of exit codes of its jobs.
What can I do is that instead of
exit 1
I will create file and do and Healthcheck in Dockerfile to monitor this file. Unfortunatelly this will mark container as unhealty, but will not exit dumb-init process.Any idea?
Thanks
The text was updated successfully, but these errors were encountered: