Docker Beginner About 20 min +140 XP

Web Container Exits After Startup

The launch API's container exits with status 0 a moment after every start, so nothing is serving.

Stage 1 of 4 in Platform Recovery Ladder.

Briefing

Northstar's platform team is standing up the launch API on a fresh host, and nothing downstream (networking, storage, the move to Kubernetes) can be tested until one API container stays up.

The image built cleanly about fifteen minutes ago and a container was created from it straight away.

That container stopped almost immediately with exit status 0 and stayed stopped.

Dev reads the clean exit as the app shutting itself down politely over an unset environment variable, which is how the service behaved on the old hosts.

The fix is yours to find: hints, the recovery checks and the debrief unlock inside the incident.

How it plays

  1. 01

    Get paged

    The alert fires and the clock starts. Read the page and the briefing.

  2. 02

    Investigate

    Work in a simulated shell with realistic output: logs, configs, services.

  3. 03

    Fix it

    Change the system the way you would in production. Hints are there if you get stuck.

  4. 04

    Prove it

    Automated checks verify the recovery, then the debrief explains what happened.

Your pager is ready.

Free, instant, and it works on your phone. No signup: start as a guest and save your progress later.