Skip to content
← Board

Container restarts in a loop after deploying

Outcome submittedDemoTeam Aurora asked · Team Maple is helping

Blocker details

Posted by Priya Nair, Team Aurora · Table 4 · 10:02 a.m.

The dashboard container starts, then restarts every few seconds on the VM.

What they already tried

Checked the logs and rebuilt the image.

  • deployment
  • docker

This thread is visible to both teams and organizers.

Help thread

  1. Team Aurora posted this blocker · 10:02 a.m.

  2. Team Maple is helping · 10:06 a.m.

  3. Sam Okafor Team Maple · 10:08 a.m. · #8

    Hi! Can you paste the health check from your compose file?

  4. Priya Nair Team Aurora · 10:11 a.m. · #9

    healthcheck:
      test: ["CMD", "curl", "-f", "http://localhost:8080/health"]
      interval: 10s
      retries: 3
  5. Tom Becker Team Aurora · 10:13 a.m. · #10

    Our server listens on 3000 now. We changed it on Friday night.

  6. Sam Okafor Team Maple · 10:15 a.m. · #11

    That's it. The health check still calls port 8080, so it fails and Docker keeps restarting the container. Point it at 3000 and redeploy.

  7. Sam Okafor Team Maple · 10:16 a.m. · #12

    Meet at our table: Table 12.

  8. Priya Nair Team Aurora · 10:39 a.m. · #13

    Redeployed. It's been up for 20 minutes with no restarts.

  9. Team Maple submitted an outcome · 10:41 a.m.

Outcome

Submitted by Sam Okafor, Team Maple · 10:41 a.m.

Repaired the deployment configuration: the health check pointed at the wrong port, so the container kept being restarted.

Evidence: Code diff

-      test: ["CMD", "curl", "-f", "http://localhost:8080/health"]
+      test: ["CMD", "curl", "-f", "http://localhost:3000/health"]

Is it fixed?

Only Team Aurora can answer. In the demo, you answer for them.

Demo only: confirming changes this page and sends nothing. “Not fixed yet” is turned off.