Docker · ECS · Intermediate
Health check calls a missing tool
Containers serve traffic briefly but are repeatedly marked unhealthy.
INITIAL ALERT
Containers serve traffic briefly but are repeatedly marked unhealthy.
You are primary on-call. Establish the failure domain, protect healthy capacity, and choose the safest next action.
The application endpoint returns 200 from outside the container.
The decisive evidence and solution remain locked inside the simulation.WHAT THIS TESTS
Production judgment across Docker · ECS.
A running host does not prove a viable container. Responders must follow the image, runtime contract, resource controls, and orchestrator health model.
- 01Read container lifecycle and exit evidence
- 02Separate host health from container health
- 03Fix runtime contracts while preserving hardening
SIMULATION STRUCTURE
Four evidence layers. No answer shown here.
The full exercise unlocks each layer as you commit to decisions.
Alert
Confirm the reported symptom and customer impact.
Baseline
Compare the failing path with a known-good condition.
Finding
Identify the evidence that separates plausible causes.
Change
Choose a controlled recovery and a durable prevention step.
Can you make the call without seeing the solution?
Try three incidents free. Paid incidents unlock only after Stripe confirms lifetime access.