# MCP Docker containers fail with name conflicts after Oct 29 update

**URL:** <https://forum.cursor.com/t/mcp-docker-containers-fail-with-name-conflicts-after-oct-29-update/139592>\
**Category:** Bug Reports\
**Created:** [October 29, 2025, 9:54pm UTC](https://forum.cursor.com/t/mcp-docker-containers-fail-with-name-conflicts-after-oct-29-update/139592 "2025-10-29T21:54:32Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [October 30, 2025, 3:47pm UTC](https://forum.cursor.com/t/mcp-docker-containers-fail-with-name-conflicts-after-oct-29-update/139592/2 "2025-10-30T15:47:19Z")

</div>

Hey, thanks for the report. This is a confirmed regression in Cursor 2.0.34 affecting MCP client initialization.

We found a related report with the same root cause: [MCP Server Race Condition Causes Infinite Process Spawning on Windows (Cursor 2.0.34)](https://forum.cursor.com/t/mcp-server-race-condition-causes-infinite-process-spawning-on-windows-cursor-2-0-34/139610)

The MCP extension spawns duplicate client instances before the first connection completes, causing:

- Docker container name conflicts (your case)
- Infinite Node.js process spawning on Windows (other report)

Your workaround using unique container names is solid and should help until a fix is released. I’m escalating both reports to the engineering team since this is a critical infrastructure issue.

I’ll update the thread as soon as there’s progress. Thanks for the logs and clear reproduction steps!

---

_[View the full topic](https://forum.cursor.com/t/mcp-docker-containers-fail-with-name-conflicts-after-oct-29-update/139592)._
