Chronos
Chronos is a lightweight Docker container for running and scheduling Python 3.7 scripts, with isolated virtual environments, a script editor, pip dependency…
Platform availability
Available on 1 of 9 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)
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.
21/100 Low
- Maintained
- 0GitHub repository is archived
- Popular
- 3876 GitHub stars
- Easy to install
- 351 install platform, install notes, Docker image
- Light to run
- 304 GB minimum RAM
Availability: platform listings confirmed today, links checked 10 days ago
- GitHub stars
- 76
- Open issues
- 0
- Last commit
- 2023-02-20
- License
- MIT
- Activity
- stale
Checked 7 days ago - source: GitHub (simse/chronos)
Resources & Compatibility
Minimum requirements: 4 GB RAM. ARM (e.g. Raspberry Pi) is not supported.
Checked 14 days ago - source: Docker Hub image tags and published docs
First-install notes
- Start the Linux agent service On Linux, run `sudo service calyptia-fluent-bit start` after install so the agent keeps collecting data in the background; if you skip this, it may not start automatically and no data will be sent. source
- Verify the Windows agent runs After an EXE or MSI install on Windows, run the dummy-output command in PowerShell to make sure Fluent Bit can start; if it errors, the agent didn't install correctly and no data will flow. source
- Install the macOS package with admin On macOS, install the downloaded .pkg with `sudo installer` and target /usr/local/bin/ so the agent is placed where the system expects it; without admin rights, the install can fail and the agent will be missing. source
- Docker installation Pull simsemand/chronos and run it with port 5000 published and a config volume mounted at /chronos; keep it private. source
- Security Do not expose Chronos to the public internet; the README warns that it currently has no authentication or protection against unauthorized access. source
- Docker run Pull the simsemand/chronos image, then map port 5000 and mount a persistent config directory. Example: docker run -p 5000:5000 -v /path/to/config:/chronos simsemand/chronos source
Fetched today - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Which port should I publish when running Chronos with Docker?
Publish the host port 5000 to container port 5000.
Can I expose the Chronos web UI to the public internet?
No. The README says not to expose it publicly because it has zero security against unauthorized access, so attackers could execute malicious code on the server.
Can Chronos run long-lived services or listen on network ports?
It is not intended for larger Python scripts meant to run forever, or for scripts that listen on ports, yet.
How are Python dependencies kept separate between scripts?
Each script gets its own virtual environment and folder, so Pip dependencies can be installed without conflicting with other scripts.
What scheduling triggers does Chronos support?
It supports interval triggers and CRON triggers.
Answers sourced from github.com
Community
- Centralized cron? : r/selfhosted - Reddit (reddit)
- Lightweight opensource selfhosted scheduler? : r/selfhosted - Reddit (reddit)
Collected 9 days ago - public community threads