The container exits immediately and the logs are empty
A newly containerized service starts and exits within a second. The platform shows it restarting repeatedly. `docker logs` prints nothing. The developer says it works when they run it locally with `npm start`.
The fix that looks right
Adding a restart policy, or increasing the restart backoff, so the container "keeps trying". It converts a loud, instantly diagnosable failure into a slow flapping service that appears in dashboards as intermittent unavailability, and the empty log — the actual clue — is now buried under a hundred identical restarts. The related version is wrapping the command in sh -c "... || sleep infinity" to keep the container alive so you can exec into it: now the platform believes the service is healthy and routes traffic to a container running nothing.