swarm-cronjob VS ofelia

Anything from simple crontab entry to something like this: https://crazymax.dev/swarm-cronjob/

So, I found a really nice little tool that solves a problem I have in a really nice way. Specifically, cron jobs on Docker Swarm. This project: https://github.com/crazy-max/swarm-cronjob It uses labels on your services to schedule jobs. Thus it needs access to the docker api, and all the security concerns that go along with it...

As i said, if it's not exposed to the outside world and doesn't work with untrusted data, that claim is not entirely valid.

Imagine something like this getting abandoned, or someone running a year old version of it: https://github.com/crazy-max/swarm-cronjob/blob/master/READM...

Its only job is to run containers on a particular schedule, no more no less. There are very few attack vectors for something like that, considering that it doesn't talk to the outside world, nor processes any user input data.

Then again, it's not my job to pass judgement on situations like that, merely acknowledge that they exist and therefore the consequences of those suddenly breaking cannot be ignored.

I also found swarm-cronjob and ofelia both seems promising. BUT , I really like the idea of an interface to watch log files etc.

To anybody that is familiar with Ofelia: how do you use different log files for different jobs?

I've been trying to figure out how to run cron jobs in my docker containers. Most of the solutions I see are some version of "make a separate container to run your crons". One version of this solution is ofelia, which people seem to like a lot.

If you want to run periodic commands on your containers, have you considered using a cron replacement (ofelia chadburn or maybe docker-crontab?

I found Ofelia but from the quick glance I took at their documentation it seems it don't allow to set scheduling rules from the docker compose.

I'm in the exact same situation. I'm currently trying to get mcuadros/ofelia installed to run as a scheduler within Docker. Here's a sample file for Ofelia to run the photoprism import (jobs.ini): https://dl.photoprism.org/docker/scheduler/

Not exactly using the OS' crontab but if you're using Docker to deploy your Django, you might actually find it cleaner to use something like Ofelia to run commands in your Django container.

If you'd like to have this schedule as part of your docker setup as well look into Ofelia https://github.com/mcuadros/ofelia You can run commands - local (on the host or on the docker container Ofelia runs in - by 'docker exec' in an existing container - by spinning up a new container

# See https://github.com/mcuadros/ofelia/blob/master/docs/jobs.md for job settings!

I'm trying to push some Information to an API on a scheduled basis. I figured ofelia is exactly what I need. A Test with "echo test" as command worked just fine, I could see the output in the logs.No if I try to run a curl command I get the following error:2022-01-27T11:30:09.008Z common.go:121 ▶ ERROR [Job "dyndns-kasm" (b5d84c412e5f)] Finished in "1.014721ms", failed: true, skipped: false, error: exec: "curl": executable file not found in $PATH

I am setting up some Wagtail and my custom management commands to be run periodically on my project's Docker container using Ofelia.