temporalio / temporalio/temporal
Feature: implement docker healthcheck
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
Is your feature request related to a problem? Please describe.
Currently docker will assume the container is ready once it is running, while the temporal engine is still warming up, leading to all sorts of problems.
Describe the solution you'd like
Implement the HEALTHCHECK directive in your Dockerfile(s).
Describe alternatives you've considered
Restarting clients.
Additional context
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Inspect the repository's Dockerfile(s) and the container startup behavior to understand when the Temporal engine is ready. Run the container and verify that the Docker HEALTHCHECK reports the appropriate readiness state during startup and after the engine is ready.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100