ofelia VS Moby

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.

Having been featured in our February 2023, and January 2024 Release Radars, Moby is the original Linux Container runtime. This new version adds a bunch of changes to the Docker CLI and Moby itself with additional features. There's bug fixes and enhancements, with the main thing for users to be on the look out for containers that were created using Docker Engine 25.0.0. These containers might have duplicate MAC addresses, and thus must be recreated. The same goes for those containers created with Moby 25.0+ and with user defined MAC addresses. Read up on all these changes in the release notes.

Formlabs does this as well for their 3d printers, my earliest encounter of this was when Docker started getting popular: https://github.com/moby/moby/blob/master/pkg/namesgenerator/...

Try to use moby instead since that is the engine in Docker.

https://github.com/moby/moby

> Podman is designed to help with this by providing stronger default security settings compared to Docker. Features like rootless containers, user namespaces, and seccomp profiles, while available in Docker, aren't enabled by default and often require extra setup.

Seccomp has been enabled by default since 2015: https://github.com/moby/moby/pull/18780

It is true that Rootless isn't enabled by default but its "extra setup" can be done with a single command (`dockerd-rootless-setuptool.sh install`)

Perhaps.

Thing is, https://github.com/moby/moby/blob/670bc0a46c4ca03b75f1e72f73... is using https://github.com/mistifyio/go-zfs which features code like `out, err := zfsOutput("get", "-H", key, d.Name)` (Source: https://github.com/mistifyio/go-zfs/blob/master/zfs.go#L315) to get a single zfs property.

Somebody chose to use a library as abstraction that looks good but is implemented as a MVP (nothing wrong with that). "In the future, we hope to work directly with libzfs" should have raised an alarm somewhere, though.

AppArmor can restrict /proc and this is even used by docker: https://github.com/moby/moby/blob/master/contrib/apparmor/te...