I built "boss levels" for my Linux & Docker game: you're on call and prod is down

Every tutorial teaches you how to start a container. Almost none teach you what to do when one is down at 3am and people are waiting. So I added "boss levels" to DockerLinux, my free game for learning Linux and Docker in a simulated terminal (here's what shipped last time). Type oncall and you take the pager. What it looks like The page. A ticket arrives: SEV-1 · INC-101 · The shop is down. Support says customers can't load the shop; an ops bot mentions the server rebooted at 03:12 for kernel updates. You're on prod-01. The terminal logs in to a pretend production server where something is broken, and a clock starts (5 minutes for this one). Your own machine is untouched and comes back afterwards. You investigate with real commands: docker ps -a, docker logs, curl, docker network inspect. There's a runbook.md to cat, and hints if you're stuck (they cost XP). You fix it, any correct way. Broken containers crash again on restart, like real ones, so "just restart it"