-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
Fix docker issues with global and dead tasks #1167
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🐯
@vdemeester we could get this one in v1.2 right ? |
@emilevauge I think so |
b84f030
to
69f939d
Compare
Rebased on branch v1.2. |
@emilevauge I'll look into doing that asap. I've also been using this branch on a local swarm cluster for about a week now and didn't run into any issue yet with both replicated and global services. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, good work on the test, very clear and easy to understand...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Thanks @christopherobin !
3be508c
to
d342ae6
Compare
A couple small issues with Docker fixed in this PR:
docker service create --mode global
) do not have aSlot
ID in the task list, so each entry will end up having the same name in the backend configuration making the docker provider crash. This fallbacks to using theTaskID
instead if the service is global.desired-state: running
filter to the task list query so that we only use alive tasks as backends.Fixes #1138