What are you trying to do?
docker run -i allows users to run images that accept ongoing communication on stdin. as far as i can tell, this is not currently possible in dagger - you can't pass the CLI host's stdin to an engine-ran process.
Why is this important to you?
MCP servers all use stdio as transport, but stdio servers can also be useful for greenfield server development.
Using the existing MCP server ecosystem with an agent running in dagger would also be hypothetically convenient.
How are you currently working around this?
Not building using dagger for these applications, or writing an SSE MCP server and using a proxy running in docker to translate the SSE events to stdio.
What are you trying to do?
docker run -iallows users to run images that accept ongoing communication on stdin. as far as i can tell, this is not currently possible in dagger - you can't pass the CLI host's stdin to an engine-ran process.Why is this important to you?
MCP servers all use stdio as transport, but stdio servers can also be useful for greenfield server development.
Using the existing MCP server ecosystem with an agent running in dagger would also be hypothetically convenient.
How are you currently working around this?
Not building using dagger for these applications, or writing an SSE MCP server and using a proxy running in docker to translate the SSE events to stdio.