[Feature Request] Allow live-restore in swarm mode cluster.
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 3.7k
- Forks
- 676
- Avg merge
- 4d 9h
- Merged PRs (30d)
- 6
Description
The docker daemon live-restore option is not compatible with swarm mode cluster, --live-restore daemon configuration is incompatible with swarm mode. I guess the live-restore is conflict with the swarmkit orchestration on judging the node healthy and migrating service's tasks. When the node's dockerd exit, the node's tasks will be migrated. But live-restore is useful on upgrading docker daemon in production environment. So will live-restore support in swarm mode cluster? Can we specify the node's heartbeat time for node failure for prevent task migrate on upgrading node.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The request concerns Docker's live-restore behavior with swarm mode, but it names no source files, tests, or entry points. First confirm whether this belongs in swarmkit rather than docker/docker, then trace node health and task migration behavior; done would require an agreed design and working support for daemon upgrades without unintended task migration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- devops, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100