[Server]: Report if container runtime is running in health endpoint
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.2k
- Forks
- 300
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 184
Description
Related to this bug for ToolHive Studio: https://github.com/StacklokLabs/toolhive-react/issues/81
If we try to start the server and a supported container runtime is not started, thv panics:
./bin/darwin-arm64/thv serve
8:59AM ERR failed to create lifecycle manager: no supported container runtime available: container runtime not found
panic: failed to create lifecycle manager: %v
The request is to allow the server to start without the container runtime (defer this check to request time?), and instead report the status of the container runtime via the /health endpoint.
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
Start with the thv serve startup path and the lifecycle manager initialization, then trace the /health endpoint. Check how the supported container runtime is detected and how the current panic is triggered. Done means the server starts without a runtime and /health reports whether the runtime is running.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100