-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Jobs are not deregistered when bringing down a docker container #76
Comments
I can confirm the issue, and in the same manner, jobs are not updated also, if you modify a label and restart the compose project / container. Currently tested with a docker-compose project not in a docker swarm environment. |
FYI, I have since switched to https://github.com/funkyfuture/deck-chores which doesn't appear to suffer from such fundamental issues. |
Thanks, but deck-shores is only an "ofelia.job-exec", there is no way to trigger new containers like "ofelia.job-run";, and it looks like ofelia has a "better" docker swarm support in theory. However, it looks like that issue ruined all benefits, because basically it needs a restart each time a new container with labels is turned on / off / modified, and it's currently not supported. Maybe, I can hack something using docker-gen. |
Reported issue should be fixed, but i assume that now configured jobs are also removed. Need to have a look |
I compiled the Docker image locally, and will use it on the next few days to see if I encounter some weird behaviour. I did some basic tests and I confirm that:
Thx |
It seems that the associated tasks are removed if a docker compose project has been stopped, but I do get at least 3 email warning before ofelia noticed the change. I used the edge image from yesterday. Labels:
|
I have a strange issue that I can't work out.
Docker discovery is working and jobs are registered when I bring up containers with ofelia labels. However, now that I have multiple jobs for multiple containers across several docker compose projects, I am finding that when I bring down those containers, the associated jobs do not get deregistered as expected. This leads to "No such container" errors next time a job is due...
The weird thing is that I tested the registration/deregistration of jobs not long ago and it all seemed to be working (in fact I chose the netresearch fork precisely because it doesn't work with the mcuadros image).
What could be causing ofelia to miss docker events or otherwise fail to deregister jobs?
Config:
The text was updated successfully, but these errors were encountered: