@KZ but that hasn't anything to do with Internet connectivity, right?
@KZ but that hasn't anything to do with Internet connectivity, right?
sleepAfter to "10m" but it seems to be inactive in 1-2 mins alwaysfetch()ing to the Container throws a Container port not found error even after a while the Container has this.ctx.container!.start()ed, which is causing startAndWaitForPorts() to time out.Error checking 8000: The container is not listening in the TCP address 10.0.0.1:8000. Anybody else receive these error messages when trying to connect to a container?The image "./Dockerfile" does not appear to be a valid path to a DockerfileContainer port not foundthis.ctx.container!.start()startAndWaitForPorts()docker run -p 8000:8000 motherduck-sse-mcp-amd64
WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
[motherduck] INFO - 🦆 MotherDuck MCP Server v0.6.2
[motherduck] INFO - Ready to execute SQL queries via DuckDB/MotherDuck
[motherduck] INFO - Starting MotherDuck MCP Server
[motherduck] INFO - Using MotherDuck token to connect to database `md:`
[motherduck] INFO - Connecting to MotherDuck in SaaS mode
[motherduck] INFO - Database client initialized in `motherduck` mode
[motherduck] INFO - 🔌 Connecting to motherduck database
[motherduck] INFO - ✅ Successfully connected to motherduck database
[motherduck] INFO - Registering handlers
[motherduck] INFO - MCP server initialized in sse mode
[motherduck] INFO - 🦆 Connect to MotherDuck MCP Server at http://0.0.0.0:8000/sse
[uvicorn] INFO - Started server process [18]
[uvicorn] INFO - Waiting for application startup.
[uvicorn] INFO - Application startup complete.
[uvicorn] INFO - Uvicorn running on http://0.0.0.0:8000 (Press CTRL+C to quit)Error checking 8000: The container is not listening in the TCP address 10.0.0.1:8000