You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix no exposed ports specified in options.ExposedPorts bug (#798)
As part of the network isolation changes, an assumption was introduced that all MCP servers have an exposed port. This is not the case for stdio - the proxy runner attaches to a stdio MCP server via the container's stdin/stdout. When the new code was run with a stdio container, the MCP container would run, the proxy runner process would die, and the following error would appear in the logs - `Error: failed to set up transport: failed to create container: no exposed ports specified in options.ExposedPorts.`
This PR changes the logic to skip parsing the exposed ports when the transport type is stdio.
0 commit comments