Q: Your Docker Compose file defines 15 services, but during local development, you only need 4 of them running. Starting all 15 wastes resources and slows down your machine. How do you selectively start subsets of services without maintaining multiple Compose files?
Use Compose Profiles (introduced in Docker Compose v1.28):
#Docker #Must enable BuildKit #L2 #Containers #Linux #Grafana
🎙️ Candidate Opening & Architectural Context
""In an interview, I explain how we diagnosed container runtime failures without guessing. The interviewer is testing: Docker Compose profiles.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third.""
Advertisement
🛠️ Production Runbook & Step-by-Step Resolution
1️⃣
Initial Diagnostics & Root Cause Analysis
Use Compose Profiles (introduced in Docker Compose v1.28):
docker compose up— starts only services without profiles (api).docker compose --profile backend up— starts api + worker.docker compose --profile full up— starts everything.
2️⃣
Remediation & Permanent Safeguards
Services without a profiles key always start. Services with profiles only start when that profile is explicitly activated: This is cleaner than docker compose up service1 service2 because profiles logically group related services and can be combined.
services:
api:
image: myapi
# No profile = always starts
worker:
image: myworker
profiles: ["full", "backend"]
ml-engine:
image: ml-engine
profiles: ["full", "ml"]
monitoring:
image: grafana
profiles: ["full", "debug"]
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: docker compose up — starts only services without profiles (api).."
⚡ 60-Second Elevator Pitch Talking Points
- docker compose up — starts only services without profiles (api).
- docker compose --profile backend up — starts api + worker.
- docker compose --profile full up — starts everything.
Advertisement