Run a Cron Job Inside of a Docker Container: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 10: Line 10:
=Overview=
=Overview=


The procedure consists in building an image that contains cron, and that runs the cron daemon in foreground as shown below:
The procedure consists in building an image that contains cron and that runs the cron daemon in foreground. If we want to use the standard pattern of configuring the application that runs in a container with environment variables, and assuming that the "application" is the job that is periodically run by cron, we need to launch cron with a script that collects required environment variables and places them in /etc/crontab, to be made available to the job. This is because cron controls the environment of the jobs that manage, and they do not have access to the standard environment.
 
/usr/sbin/crond -n
 
The daemon is configured to run in foreground, and also <font color=red>to log into syslog instead of sending e-mails (not tested)</font>.


=Dockerfile=
=Dockerfile=

Revision as of 21:10, 15 February 2018

External

Internal

Overview

The procedure consists in building an image that contains cron and that runs the cron daemon in foreground. If we want to use the standard pattern of configuring the application that runs in a container with environment variables, and assuming that the "application" is the job that is periodically run by cron, we need to launch cron with a script that collects required environment variables and places them in /etc/crontab, to be made available to the job. This is because cron controls the environment of the jobs that manage, and they do not have access to the standard environment.

Dockerfile

FROM centos:latest
RUN yum install -y crontabs logrotate
RUN echo "* * * * * root /opt/activity >> /tmp/cron.log 2>&1" >> /etc/crontab
COPY ./activity /opt/activity
ENTRYPOINT ["/usr/sbin/crond", "-n"]

cron Job Output

We do not want crond to e-mail stdout/stderr of the jobs it runs, but rather to log them locally, as shown here.

Note that this will write into the writable layer of the container, so either we should design the cron jobs to output nothing on success, and only use this mechanism for debugging.