0
I deployed a Node.js service inside a Docker container, and after fixing a dependency issue that was causing crashes, the container still enters a restart loop. I checked the logs with docker logs <container_id> and saw exit code 1, but the code itself runs fine when I execute it locally.
Could this be a resource limit problem—like hitting the memory cap set by Docker Desktop—or is there a misconfiguration in the HEALTHCHECK instruction that's tricking the daemon into thinking the app is unhealthy? I've also noticed that setting --restart unless-stopped didn't prevent the rapid cycling. What diagnostic steps should I take to isolate whether the issue is inside the container runtime or the application itself?
