Docker Configuration Validation

IMPORTANT: When this command is invoked, you MUST actually READ and CHECK the files. Do NOT just describe what to check - PERFORM THE CHECKS.

Step 1: Find Docker Files

Use Glob to find all Docker-related files:

docker/docker-compose.prod.yml
docker/nginx/nginx.conf
docker/nginx/Dockerfile
docker/env/.env.example.*
docker/monitoring/**/*
{backend}/Dockerfile
{frontend}/Dockerfile
.dockerignore

Step 2: Required File Checks

For each file, report:

• ✅ EXISTS: {filepath}
• ❌ MISSING: {filepath}

Step 3: docker-compose.prod.yml Validation

READ the file and check each service for:

Health Checks (REQUIRED)

# Each service MUST have:
healthcheck:
  test: ["CMD", ...]
  interval: ...
  timeout: ...

Report:

• ✅ Service '{name}' has health check
• ❌ Service '{name}' MISSING health check

Resource Limits (REQUIRED for production)

# Each service MUST have:
deploy:
  resources:
    limits:
      cpus: ...
      memory: ...

Report:

• ✅ Service '{name}' has resource limits
• ⚠️ Service '{name}' missing resource limits

Depends On with Condition

# Services should use:
depends_on:
  database:
    condition: service_healthy

Report:

• ✅ Service '{name}' uses condition: service_healthy
• ⚠️ Service '{name}' uses depends_on without condition

Network Configuration

• ✅ Custom network defined (not 'default')
• ❌ No custom network defined

Volume Definitions

• ✅ All volume references defined in 'volumes:' section
• ❌ Volume '{name}' referenced but not defined

Step 4: Nginx Configuration Validation

READ docker/nginx/nginx.conf and check:

Check	Pattern to Find	Status
Upstream block	upstream backend_servers	✅/❌
Health endpoint	location /health	✅/❌
Rate limiting	limit_req_zone	✅/❌
Security headers	add_header X-Frame-Options	✅/❌
Gzip enabled	gzip on	✅/❌
Proxy headers	proxy_set_header X-Real-IP	✅/❌

Step 5: Dockerfile Validation

For each Dockerfile, check:

Check	How to Verify	Status
Multi-stage	Has multiple FROM statements	✅/❌
Non-root user	Has USER instruction (not root)	✅/❌
Health check	Has HEALTHCHECK instruction	✅/⚠️
.dockerignore	File exists in same directory	✅/❌

Step 6: Environment File Validation

For each .env.example.* file:

Check	How to Verify	Status
No real secrets	Values contain CHANGE_ME or placeholder	✅/❌
Has comments	Has documentation comments	✅/⚠️
Required vars	Has DB_, REDIS_, JWT_* as needed	✅/⚠️

Step 7: Output Validation Report

FORMAT YOUR OUTPUT EXACTLY LIKE THIS:

╔══════════════════════════════════════════════════════════════╗
║           DOCKER CONFIGURATION VALIDATION REPORT             ║
╚══════════════════════════════════════════════════════════════╝

📁 FILE EXISTENCE CHECK
────────────────────────
✅ docker/docker-compose.prod.yml
✅ docker/nginx/nginx.conf
✅ docker/nginx/Dockerfile
❌ docker/env/.env.example.grafana (MISSING)
✅ src/backend/Dockerfile
❌ src/frontend/Dockerfile (MISSING)

📋 DOCKER-COMPOSE.PROD.YML
────────────────────────
Service: nginx
  ✅ Health check configured
  ✅ Resource limits set
  ✅ Network assigned

Service: backend-1
  ✅ Health check configured
  ✅ Resource limits set
  ✅ Depends on database (condition: service_healthy)

Service: redis
  ✅ Health check configured
  ⚠️ Missing resource limits

🔧 NGINX.CONF
────────────────────────
✅ Upstream backend_servers defined
✅ Rate limiting configured (limit_req_zone)
✅ Security headers present (X-Frame-Options, X-Content-Type-Options)
✅ Gzip compression enabled
✅ Proxy headers configured

🐳 DOCKERFILES
────────────────────────
Backend (src/backend/Dockerfile):
  ✅ Multi-stage build
  ✅ Non-root user (appuser)
  ✅ HEALTHCHECK instruction
  ✅ .dockerignore present

Frontend (src/frontend/Dockerfile):
  ❌ FILE NOT FOUND

📊 SUMMARY
────────────────────────
Passed:  15
Warnings: 2
Failed:   3

🔧 REQUIRED FIXES
────────────────────────
1. Create docker/env/.env.example.grafana
2. Create src/frontend/Dockerfile
3. Add resource limits to 'redis' service

⚠️ RECOMMENDATIONS
────────────────────────
1. Consider adding HEALTHCHECK to frontend Dockerfile

CRITICAL REMINDER

This command MUST:

1. USE Read tool to examine each file
2. ACTUALLY parse and check the content
3. REPORT specific findings (not generic advice)
4. PROVIDE line numbers when reporting issues
5. OUTPUT a structured report with symbols (✅ ⚠️ ❌)

DO NOT just list what should be checked. ACTUALLY READ AND CHECK THE FILES.