Cron Alpine

Cron Alpine is a lightweight Docker container that runs a BusyBox crond daemon for scheduling cron jobs.

  • Automation
  • Other
  • Productivity
  • Tools & Utilities
Cron Alpine is a lightweight Docker container that runs a BusyBox crond daemon for scheduling cron jobs. Mount a crontab file to define jobs, making it ideal for simple task automation in minimal container environments.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

41/100 Fair

Maintained
38last commit 349 days ago
Popular
144 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
100128 MB minimum RAM

Availability: platform listings confirmed today, links checked 23 days ago

GitHub stars
4
Open issues
1
Last commit
2025-12-06
Latest release
v3.6.1
License
GPL-3.0
Activity
stale

Checked 7 days ago - source: GitHub (2franix/cron-docker)

Resources & Compatibility

Minimum requirements: 128 MB RAM, 1 GB disk.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Install node-cron before starting Run npm install node-cron in the project folder so the app has the scheduling package. Without it, the program will stop before it can create or run any cron jobs. source
  • Set timezone and block overlapping jobs When defining a job, set timezone and noOverlap: true. This prevents runs from happening at the wrong local time and stops a long job from starting a second copy while the first is still going. source
  • Add a simple test job first Start with a basic 'run every minute' test job so you can see something happen. This is a quick way to confirm the scheduler is actually working before you add important tasks. source
  • Mount crontab file Create a crontab file and mount it to /crontab in the container; the BusyBox crond daemon reads jobs from this file on each cycle. source

Fetched 47 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How do I provide the crontab to the container?

Create a crontab file and bind mount it into the container, for example at /crontab. The image installs the crontab file specified by CRON_SPEC_FILE as the worker user's crontab at startup.

Why does editing the mounted crontab file not change the running schedule?

The crontab is installed only when the container starts. Changing the mounted file while the container is running does not have any effect on cron.

How can I make helper scripts available to the cron job?

Mount the scripts in the worker home directory, which defaults to /worker and can be set with CRON_USER_HOME. The container changes their ownership at startup, or you can build a derived image that copies them in to avoid changing ownership on the host.

How can I run commands as root before the cron daemon starts?

Mount shell scripts in the /entrypoint.pre.d directory. They are executed in alphabetical order before the cron daemon starts.

How can I have cron job output sent by email?

Configure the SMTP_* variables and CRON_MAILTO to use msmtp. This email feature is disabled by default and is only enabled when SMTP_HOST is set.

Can I avoid storing sensitive values in environment variables?

For supported variables, store the value in a file in the container and set the corresponding XXX_FILE variable to the file path. This is useful for docker secrets, but not every variable supports the _FILE variant.

Answers sourced from github.com

Community

Collected 53 days ago - public community threads