om-dev-container-maintenance

Run the audit checklist comparing version sources like .nvmrc and package.json against the devcontainer Dockerfile, plus service parity, env var rewrites, and build sequence alignment. Fix any mismatches in the minimal affected file and update the documentation afterward.

Health check failures usually come from stale named volumes created with different credentials or versions. Wipe the affected volume with docker volume rm, then reopen the container so services reinitialize cleanly.

Numeric entries in devcontainer.json forwardPorts bind to the workspace container, not the service. Use named service syntax like "postgres:5432" and "redis:6379" in forwardPorts, then rebuild the container.

Failures typically occur at specific post-create.sh steps: volume permission errors, sed patterns in setup-env.sh not matching .env.example, missing native build tools for yarn install, or database migration conflicts. The troubleshooting guide maps each step to its diagnosis and fix.

Set WATCHPACK_POLLING and CHOKIDAR_USEPOLLING to true in the workspace service environment in docker-compose.yml. This is required for file watching to work through macOS Docker bind mounts.