Inspector 0.9.4: containers without a health check recover properly
This commit is contained in:
1 parent
57100d0a7b
commit
6aed0cf9a7
4 files changed
+49
-9
No files matched your search
@@ -7,6 +7,26 @@ Version numbers follow [Semantic Versioning](https://semver.org/spec/v2.0.0.html
|
||||
|
||||
---
|
||||
|
||||
## [0.9.4] — 2026-10-28
|
||||
|
||||
### Fixed
|
||||
|
||||
- **Containers without a Docker health check now "recover" properly.** Many images
|
||||
don't define a health check, so Docker reports them as `NO HEALTH CHECK` even when
|
||||
they work. Inspector only treated `HEALTHY` as back to normal, so for these
|
||||
containers:
|
||||
- the error count never reset, and one-off failures days apart added up to a restart;
|
||||
- no "recovered" alert was sent;
|
||||
- with *Restart, then redeploy*, the next unrelated problem skipped the restart and
|
||||
redeployed the whole stack.
|
||||
|
||||
Now `NO HEALTH CHECK` counts as working (unless you made it a restart trigger): the
|
||||
count resets, the "recovered" alert is sent ("back to running (no health check)"),
|
||||
and the next problem starts with a plain restart. Containers with a health check
|
||||
behave exactly as before.
|
||||
|
||||
---
|
||||
|
||||
## [0.9.3] — 2026-10-28
|
||||
|
||||
### Changed
|
||||
|
||||
Reference in new issue
Block a user