debug-local

Troubleshooting a Docker container that won't start involves checking Docker container statuses, inspecting container logs, and verifying environment variables to identify missing configurations or runtime errors preventing service startup.

Diagnosing auth issues in local dev environments requires validating service statuses and checking environment variables to detect misconfigurations. Proactive diagnostics route auth errors based on symptom classification to pinpoint the exact authentication failure.

Your service fails to connect when environment variables are missing because local development requires specific `.env` files for correct operation. Identifying and creating these missing environment files resolves unreachable service errors and runtime failures.

Yes, you need Docker installed to investigate local runtime errors on this platform. The diagnostic process requires direct access to the Docker environment to manage containers, check statuses, and review logs for service failures.

Yes, you can automatically classify local dev symptoms like missing env vars and service failures. Symptom classification routes issues based on user reports, categorizing missing environment variables, unreachable services, and auth errors for targeted diagnostics.

You can verify service status and check container logs without manual commands by using proactive investigation tools that automatically query Docker statuses and extract container logs, providing actionable insights into runtime errors and service failures.