mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-06 10:59:59 +00:00
kevinveenbirkenbachandClaude Opus 5
b9669fcaa5
A container without a healthcheck is accepted the moment its process starts. The restore drill asks the host's health service for its verdict, so a service that came back empty passes as long as it is running - which is how an empty volume survives a drill unnoticed. Twenty-one services get a probe and thirteen get a marker naming why none is possible: a one-shot client that exits, a build image with no service port, a media bridge on UDP. The flavor comes from each image's own layer history, read from the registry through the mirror, so no image had to be pulled to find out whether it ships curl, wget or a shell. Two entries carry more weight than the rest. The central Postgres, which every replay of the recover chain lands in, had no probe at all; it gets the pg_isready line that sys-svc-rdbms already runs for the per-app engine. And the matrix runner starts systemd within a second while its inner daemon is still pulling every image of the deployment, so it counted as healthy long before anything served - it now waits for Synapse to answer. No probe replaces one: nineteen of the twenty-one images ship no HEALTHCHECK, and the two that do already carried a declaration before this change. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
17 lines
380 B
YAML
17 lines
380 B
YAML
---
|
|
svc-container:
|
|
lifecycle: beta
|
|
required_by:
|
|
compose:
|
|
categories: [web]
|
|
swarm:
|
|
categories: [web]
|
|
# nocheck: image-healthcheck utility image run as a one-shot, no long-running process
|
|
busybox:
|
|
image: busybox
|
|
version: "1.38"
|
|
# nocheck: image-healthcheck build-time image run as a one-shot, no service port
|
|
node:
|
|
image: node
|
|
version: "26-alpine"
|