Tracks

73 labs
Shell basicsLearn to inspect before changing anything.
0 / 13
LinuxProcesses, services, storage, access, and operating evidence.
0 / 11
NetworkingFollow requests from name to socket to service.
0 / 7
GitRecover history and ship changes safely.
0 / 6
ContainersPackage and operate a process with its dependencies.
0 / 5
CI/CDProve that the artifact deployed is the artifact tested.
0 / 4
Infrastructure as codeReview plans and reconcile managed state.
0 / 3
Configuration managementConfigure fleets with repeatable changes.
0 / 3
KubernetesOperate declarative workloads and diagnose cluster failures.
0 / 7
MonitoringUse signals to narrow causes and protect users.
0 / 3
Incident responseRespond, recover, and learn from incidents.
0 / 3
SecurityReduce privilege and protect the delivery chain.
0 / 3
DatabasesKeep data reachable, correct, and recoverable.
0 / 2
CloudGrant access by identity, not by wildcard.
0 / 2
CapstoneOperate a system with simultaneous faults.
0 / 1
README.md

OpsQuest

Broken Linux machines for learning operations work. Each lab starts a private machine in your browser with something already wrong: a service that will not start, a disk that keeps filling, a deploy that shipped the wrong build. You fix it with the same commands you would use at work, then press Check my work. The checker looks at the machine itself and tells you which part is not fixed yet.

How a lab works

  1. Open a lab and press Start lab. A container boots with the problem already set up. Plain Linux labs take a few seconds; Docker and Kubernetes labs take about 30.
  2. Read the ticket. Investigate in the terminal. There is no single right command.
  3. Press Check my work. If a goal is not met, the checker says which one and why. When you pass, the lab shows other fixes that also work.

Hints open one at a time. Every lab has a Theory tab with the background, and the book chapters that cover it properly.

Where to start

If you are…Start withLevelTime
New to the command lineFind the latest handoffEasy · Do10 min
You know Linux, try a real outageIt works when Ivo runs itMedium · Fix25 min
You run containers at work3,112 events vanished in a releaseMedium · Fix30 min
You want the hardest oneFriday evening, everything at onceHard · Boss incident60 min

The setting

Every lab happens at Northstar Parcel, a made-up regional parcel carrier with seven depots, a few dozen servers, and the usual history of quick fixes. You join as the newest member of the platform team. The tracks follow your first months: the shell on your first morning, then the old server room, the network, Git, containers, the pipeline, and finally a Friday evening when everything breaks at once.

The people and systems recur from lab to lab. Mara runs the on-call rotation, Ivo writes most of the backend, Sasha owns the platform, and Priya is the one person in security. Waybill tracks parcels, Ledger settles payments with carriers, Docklight queues warehouse events, and Gatehouse is the edge proxy in front of all of it.