-
Notifications
You must be signed in to change notification settings - Fork 27
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
A replacing Docker-Compose service container's (diverging) jobs are ignored #114
Comments
i cannot reproduce what you describe. please invoke deck-chores in debug mode and post its output here.
|
Hi @funkyfuture, Log
|
a'ight, so what's happening is that (to me somewhat unexpected) the replacing container is already found when its start hasn't been processed yet. and the then executed so, as a workaround, just don't hurry. kill the old container first, give i don't know when i will look into fixing this, might be a couple of months. i'm happy to review Pull Requests with a solution and can be of informative assistance beforehand, just ask. note: i spotted a new (to me) label on the containers in the |
Summary
If I change the time interval in
compose.yaml
, the job is not rescheduled.If I change the command in
compose.yaml
, the job command doesn't change.Reproduction
docker run -it -v /var/run/docker.sock:/var/run/docker.sock -e TZ=UTC funkyfuture/deck-chores:1.3.10
.compose1.yaml
compose2.yaml
docker-compose -f compose1.yaml up -d; docker-compose -f compose2.yaml up -d
.Expected behavior
After changing labels and redeploying, jobs should change.
Actual behavior
After changing labels and redeploying, jobs remain the same.
Versions
Additional
Maybe related to #113.
The text was updated successfully, but these errors were encountered: