Node shutdown, how to know the reason. (docker log -f + docker service ps are not enough)
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 3.7k
- Forks
- 676
- Avg merge
- 4d 9h
- Merged PRs (30d)
- 6
Description
I have a service run with scale of 4 across 4 VMs.
Problem
At some point, the node (container) shutdown, with some reason that I do not know.
I try to look at the log of such existed containers by using
$docker log EXISTED_CON_ID
#and
$docker service ps SERVICE_NAME
Both show me the output which is quite normal, nothing seemed to be a cause to the problem.
Especially, docker service ps shows me no any ERROR on that shutdown node.
BTW, swarm works well in maintaining the scale after that.
Question
How can I see more log, or is there a better way to figure out what actually happen, e.g. swam log?
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
No files, tests, or entry points are mentioned. Start by reviewing SwarmKit node and task shutdown handling alongside Docker and service logs; done means identifying where the shutdown reason is recorded or documenting a reliable way to retrieve it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- distributed-systems, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100