0 if all active components are healthy, 1 if any are unhealthy.
What it checks
nanny health checks three things:
A component that was never started is not checked and does not cause a non-zero exit.
nanny health only reports on what is active.
This means nanny health run from a regular terminal (outside nanny run) will typically show local bridge: not running — that’s expected. The bridge env vars are injected by nanny run into the child process, not into the terminal that launched it.
Example output
Server running, certs valid:1 when any active component is unreachable.
Certificate expiry warning
When certs exist and are valid but expire within 30 days,nanny health prints a warning to stderr:
0 — a near-expiry cert is healthy, just worth knowing about.
Use in scripts and health checks
nanny health is designed for scripts, Docker health checks, and Kubernetes liveness probes:
Docker:
See also
nanny server status— focused status view for the governance servernanny certs show— cert expiry and file inventory