Skip to content

Marking a container unhealthy didn't stop it from taking traffic

7.8 relevance
Score Breakdown
technical depth
9
novelty
7
actionability
9
community
5
strategic
5
personal
9

Scored daily by a customisable AI persona to surface the most relevant engineering leadership news.

Deep dive into container health check failure with nginx proxy_next_upstream bug, highly actionable for cloud infrastructure and observability.

AI/ML dev.to
Marking a container unhealthy didn't stop it from taking traffic
Summary

Docker's HEALTHCHECK flag is purely informational and does not affect traffic routing or container lifecycle. An nginx reverse proxy will continue sending requests to an unhealthy container as long as its TCP connections and HTTP responses succeed, and Docker's restart: always policy only triggers on process exit, not health status. The author confirmed this by running 160 requests through an unhealthy container with zero failures, and observed no restart despite 35 seconds of continuous unhealthy status.

Author

Alex Georgiev

More from Alex Georgiev →