DebugMidDevOpsAuto-graded
Make a compose stack reach Postgres and Redis
Tests whether someone traces a silent misconfiguration across several connected services instead of changing settings until something works.A three-service Compose stack — a web app, Redis and Postgres — that does not work. The web service cannot reach the database, and every Redis lookup misses. The services are all defined and all start; the wiring between them is what is wrong. Find the misconfigurations and make the stack talk to itself.25 min
docker
You're done when
- The database host points at the Compose service name rather than something unreachable from inside the network.
- The Redis host likewise resolves to its service, so the cache is actually hit.
- The Postgres password is configured, so the database accepts the connection.
- Service startup order is wired with dependencies, so the web app does not race its backing services.
What it measures
Container networkingKnowing how services address one another inside a Compose network, and why localhost is the wrong answer there.
Container orchestrationConfiguring credentials and startup dependencies so a multi-service stack comes up in a usable state.
Systematic diagnosisWorking out which of three services is at fault from the symptoms, instead of changing settings at random.
Your environment
Terminal + editorA full shell in the browser
Claude CodePre-authenticated, no key setup
Isolated microVMYours alone, wiped afterwards
Start this lab
25 min
Start labYou'll sign in to Anthropos to start. The lab opens in a private cloud workspace with Claude Code ready to use.AI Labs is part of Anthropos Workforce. Not on your plan yet? Book a demo