Docker updates hostconfig.json config.v2.json on every healthcheck result which causes permanent disk activity
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.1k
- Forks
- 2.2k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 43
Description
Container healthcheck checks results do make docker update hostconfig.json and config.v2.json on disk. If those healthcheck run regularly e.g. every 5s this causes disk activity every 5s as docker would update the config files regardless if the status has changed or not.
Having multiple containers running healthchecks this causes permanent unnecessary disk activity and decreases overall system performance.
It can be observed with the images from: pms-plex, syncthing/synchting and shinobi/shinobi.
Expected behaviour:
Writings to config files should occur only on healtheck status changes if needed at all.
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 issue names no files, tests, or entry points. Start by reproducing the periodic healthcheck behavior with a container and trace where healthcheck results persist to hostconfig.json and config.v2.json. Done means those files are not rewritten when the health status has not changed, with regression coverage for repeated unchanged results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- cli, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100