Cron jobs are essential for automating tasks, but running them inside Docker containers introduces some unique challenges. This article walks you through the correct approach to setting up, managing, and persisting cron jobs in a containerized environment.
1. Why Cron in Docker Needs Special Attention
Containers are ephemeral and often single-process focused, making traditional cron behavior tricky. Instead of running the host’s cron, we embed cron into the container, but we must make sure it stays running and logs properly.
2. Dockerfile for Cron Jobs
Here’s a sample Dockerfile that installs cron, sets up a job, and keeps the container alive:
# Dockerfile
FROM ubuntu:20.04
RUN apt-get update && \
apt-get install -y cron curl
# Create the cron job
RUN echo "*/5 * * * * root curl -s https://example.com/cron-task > /var/log/cron.log 2>&1" > /etc/cron.d/mycron
# Give execution rights
RUN chmod 0644 /etc/cron.d/mycron
# Apply cron job
RUN crontab /etc/cron.d/mycron
# Create the log file
RUN touch /var/log/cron.log
# Start cron in foreground
CMD cron -f
3. Build and Run the Docker Container
docker build -t cron-container .
docker run -d --name my-cron cron-container
The job above pings a URL every 5 minutes and writes logs to /var/log/cron.log.
4. Viewing Cron Logs
docker exec -it my-cron tail -f /var/log/cron.log
5. Alternative: Multi-process Containers
For more complex setups, you can use a process supervisor like supervisord or a shell script that starts both your app and the cron service.
Conclusion
Running cron jobs in Docker requires careful setup to avoid common pitfalls. Whether you're scheduling backups, pings, or data refresh tasks, embedding cron into containers gives you powerful automation while staying within your container ecosystem.
Enjoyed this? You can support my work here: buymeacoffee.com/hexshift