ModelEngine-Group / ModelEngine-Group/nexent
[Bug] After the addition of container MCP fails, the container still occupies resources and cannot be deleted.
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5.9k
- Forks
- 731
- Avg merge
- 19h 34m
- Merged PRs (30d)
- 172
Description
Nexent Version
2.0.0
Problem Description
When adding container MCP service fails to connect (sdk/nexent/docker/container/docker_client.py async def start_container _wait_for_service_ready ContainerConnectionError), the container keeps restarting without being deleted, causing the container to keep running and occupying resources.
Reproduction Steps
No response
Additional Information
No response
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 in sdk/nexent/docker/container/docker_client.py, reading start_container and its _wait_for_service_ready call, especially the ContainerConnectionError path. Reproduce a failed container MCP connection and trace the container state afterward; done means the failed container no longer restarts or continues occupying resources and can be deleted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- backend, infrastructure
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100