-
Notifications
You must be signed in to change notification settings - Fork 75
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
Don't run otobo_cron_1 as root #417
Comments
As cron is no longer used.
Instead run bin/otobo.Daemon.pl in a loop
Issue RotherOSS/otobo#417: rename otobo_cron_1 to otobo_daemon_1
cron is gone now. Tests look fine. Closing the issue. |
Reopening as the setup can be simplified by using the |
It's complicated. The OTOBO Daemon can't easily be run as a foreground process as bin/otobo.Daemon.pl makes an effort to run the actual Daemon as a forked process. So we stick with entrypoint.sh acting as a watchdog for the Daemon. Which is fine, as it prohibits the frequent retries that would be done by docker-compose. While investigating this it was found the the Daemon does not shut down gracefully when the otobo_daemon_1 container is stopped. This behavior has been improved by adding a handler of SIGTERM to entrypoint.sh. See also https://www.kaggle.com/residentmario/best-practices-for-propagating-signals-on-docker |
Tests look fine. The Github action has problems, but that looks unrelated. Closing the issue. |
Reopening as the feature should be backported to OTOBO 10.0.4 |
The feature will be backported in 10.0.4. The backport includes a renaming of the container from otobo_cron_1 to otobo_daemon_1. Do the renaming already for 10.0.3, in order to have as few conflicts as possible. |
Issue #417: rename otobo_cron_1 to otobo_daemon_1
Even though the command 'cron' is still running in the container.
…e_cron_to_daemon Issue RotherOSS/otobo#417: rename service 'cron' to 'daemon'
…e_cron_to_daemon Issue RotherOSS/otobo#417: rename service cron to daemon
Renaming from otobo_cron_1 to otobo_daemon_1 has been done. |
Issue #417: grab Docker related changes from the rel-10_2 branch
Issue #417: some useful changes from the rel-10_0 branch
Backporting from 10.1.x to 10.0.x has been done. |
Issue RotherOSS/otobo#417: grab some changes from rel-10_1
No problems encountered.Closing this issue. |
Higher priority is to avoid running docker containers as root. This is already the case for otobo_web_1, but should also be the case for otobo_cron_1. The most simple ide a is to get rid of cron and call in entrypoint.sh something like
watch -n 300 $HOME/bin/otobo.Daemon.pl start
Originally posted by @bschmalhofer in https://github.com/RotherOSS/otobo/issues/280#issuecomment-687583015
The text was updated successfully, but these errors were encountered: