feat(docker compose): healthcheck for speckle-server #1651
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description & motivation
For speckle deployed via Docker Compose, there are conditions where the speckle server container becomes unresponsive but has not yet exited with a non-zero exit code. For example, this issue report #1649
This Pull Request introduces a health check to the pod which will cause non-responsive pods to be automatically restarted after 30s.
This is a workaround for the symptoms (unresponsiveness of the speckle-server pod), and not a fix for the root cause.
Changes:
To-do before merge:
Screenshots:
Validation of changes:
Checklist:
References