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):
Want to master this scenario in a live sandbox? KodeKloud's Docker Certified Associate (DCA) Hands-On Lab Course covers this exact problem with hands-on terminal drills.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "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."
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.
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"]
- docker compose up — starts only services without profiles (api).
- docker compose --profile backend up — starts api + worker.
- docker compose --profile full up — starts everything.
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
-
Structuring Dockerfile instructions inefficiently by copying app source before package manifests when configuring Docker Compose file
Copying code before package manifests (
package.json,go.mod,requirements.txt) invalidates the build cache on every commit, forcing slow full reinstalls. -
Neglecting the PID 1 process reap problem and omitting proper SIGTERM signal forwarding when configuring Docker Compose file
If an application runs as PID 1 without an init system (like
tini), it fails to reap zombie child processes and ignoresSIGTERMsignals, causing unclean 10s timeouts. - Assembling single-stage images containing compilers, build SDKs, and header files in production when configuring Docker Compose file Single-stage builds bloat image size by gigabytes and expose extensive package vulnerabilities; multi-stage builds isolate artifacts into minimal distroless images.
- Confusing container port forwarding on bridge networks with unisolated host networking mode when configuring Docker Compose file Bridge networking utilizes iptables NAT translations which add latency overhead, whereas host networking bypasses the network namespace entirely.