You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently ofelia is only capable of detecting containers during startup. Stopped or destroyed containers are also not detected leading to errors like:
common.go:117 ▶ ERROR [Job "testjob" (4ffe34388a00)] Finished in "3.3764ms", failed: true, skipped: false, error: error creating exec: No such container: hopeful_gates
This could be fixed if ofelia would detect container starts and stops during its runtime which also would extend the overall utility of ofelia (maybe by polling the socket every X seconds or listening to events on the socket).
The text was updated successfully, but these errors were encountered:
I am using docker labels and ofelia reads it once and never again. If you change the command, modify the schedule, even remove the labels, it does not detect it. You have to restart ofelia, which is not great as it may be running some other job. Ideally jobs should be updated dynamically, the same way you add a task. Adding it on this feature request as I do also see the same behavior when I stop the container. The job is still being scheduled
Currently ofelia is only capable of detecting containers during startup. Stopped or destroyed containers are also not detected leading to errors like:
common.go:117 ▶ ERROR [Job "testjob" (4ffe34388a00)] Finished in "3.3764ms", failed: true, skipped: false, error: error creating exec: No such container: hopeful_gates
This could be fixed if ofelia would detect container starts and stops during its runtime which also would extend the overall utility of ofelia (maybe by polling the socket every X seconds or listening to events on the socket).
The text was updated successfully, but these errors were encountered: