2025-02-20, 08:05 AM
Thanks for that. I wasn't actually killing the container deliberately - it was being restarted by Docker (or portainer, or ... or ... well, something).
However, you've given me enough to get a win. I've added the following to the compose file:
This was enough to give the container 30m to restart, and additionally provides a reasonable health status for the container. I'll have to try a few things once I'm in front of it again, but at least it's running. Will probably see if I can propose some changes to the container deployment documentation, once I work out any remaining kinks. I think it would be helpful to have a larger example compose file with these settings, for example.
However, you've given me enough to get a win. I've added the following to the compose file:
Code:
healthcheck:
test: ["CMD", "curl", "-fs", "-S", "--max-time", "2", "http://localhost:8096"]
interval: 60s
timeout: 10s
retries: 5
start_period: 1800sThis was enough to give the container 30m to restart, and additionally provides a reasonable health status for the container. I'll have to try a few things once I'm in front of it again, but at least it's running. Will probably see if I can propose some changes to the container deployment documentation, once I work out any remaining kinks. I think it would be helpful to have a larger example compose file with these settings, for example.