Frontend rebuilds from scratch on every container start

command: bash -c "yarn build && pm2 start yarn --name nextjs ... && pm2 monit" — a full Next.js production build on every container start.

The documented deploy step is docker restart chakra-docker_chakra_frontend_1, so every deploy and every host reboot means minutes of 502, with no healthcheck so nothing notices.

pm2 monit is an interactive TUI being used as PID 1 — it holds the container open by accident, not by design. The nested quoting is also broken: "nextjs" sits inside an already double-quoted string, so the shell sees a bare nextjs (works by luck).

Fix: build at image-build time; command: pm2-runtime start yarn --name nextjs --interpreter bash -- start; add a healthcheck.

Evidence

docker-compose.yml:110-136

• Verified against: origin/master 44ca47e (2026-07-25)
• Verdict: CONFIRMED

Start by inspecting docker-compose.yml lines 110-136 and trace how the frontend image and startup command are defined. Verify the production build happens during image creation, PM2 runs with the specified non-interactive command, and a healthcheck reports frontend readiness; validate with a container restart and deployment-style startup.