ofelia icon indicating copy to clipboard operation
ofelia copied to clipboard

A docker job scheduler (aka. crontab for docker)

Results 114 ofelia issues
Sort by recently updated
recently updated
newest added

Running a job every 15 minutes causes numerous containers to spin up for the 60 seconds between X:15 and X:16. Once time hits X:17, containers stop being created. I tested...

i use the job-run to start an php container and run a php script every 5 minutes. the docker run command should be something like this: `docker container run --rm...

**Component** github.com/docker/[email protected] : Status: fixed in 23.0.3, 20.10.24 **[CVE-2023-28840](https://nvd.nist.gov/vuln/detail/CVE-2023-28840)** Moby is an open source container framework developed by Docker Inc. that is distributed as Docker, Mirantis Container Runtime, and various...

It seems that there is a hard limit of 24h being enforced on the jobs runtime (https://github.com/mcuadros/ofelia/blob/master/core/runjob.go#L221) Is there a specific reason behind this? I have some backup jobs that...

Hi It would be nice if the LogFormat could be exposed as a configuration option, the use case is to generate the log in a structured JSON equivalent format to...

Now ofelia has *-only-on-error parameters, but if a job is stuck and *-only-on-error == true, no warning notifications are received. Please add or modify the *-only-on-error parameters so that notifications...

Hello, I'm encountering an unexpected error when running scheduled jobs in WHMCS. The initial setup of the scheduler appears to be fine. The log output confirms the successful registration of...

**[CVE-2023-25153:](https://nvd.nist.gov/vuln/detail/CVE-2023-25153)** **Containerd** is an open source container runtime. Before versions 1.6.18 and 1.5.18, when importing an OCI image, there was no limit on the number of bytes read for certain...

**[CVE-2023-27561](https://nvd.nist.gov/vuln/detail/CVE-2023-27561)**: **Opencontainers 1.1.4** has Incorrect Access Control leading to Escalation of Privileges, related to _libcontainer/rootfs_linux.go._ To exploit this, an attacker must be able to spawn two containers with custom volume-mount...

If I setup and exec job on another container via labels it fails as it's unable to find my bash script. Error: StdOut: OCI runtime exec failed: exec failed: unable...