container v0.0.4 fails health check

[Harrolee]

• healthcheck goes to /api
• passes if 200 | 204 is returned

The result is that the instance is continuously shutdown and restarted.

---

Logs from the ECS task suggest that the container does not receive a healthcheck at all

• healthcheck goes from ECS(?) to fargate cluster?
• Learn what the healthcheck's response is
• 404? 401? 403?

[Harrolee]

from ECS health check docs:

The health check commands run on the container. Therefore you must include the commands in the container image.

The health check connects to the application through the container's loopback interface at localhost or 127.0.0.1. An exit code of 0 indicates success, and non-zero exit code indicates failure.

I didn't add a command to the container image...