Restart proxy processes after a reboot
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 2.2k
- Forks
- 300
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 184
Description
In #135 we added a restart policy to the MCP containers so they come back up after a reboot, but the proxy processes do not restart, so the containers aren't reachable by clients until you restart each one to re-launch the proxy.
It would be nice to handle reboots gracefully and bring back not only the container but also the proxy.
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
Review the restart policy introduced in #135, then trace how the MCP containers launch their proxy processes. Reproduce a reboot and verify that both the containers and their proxies return without manually restarting each container; confirm clients can reach them afterward.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100