Playwright for Python is not working because of unsupported platform tag

[alexeygumirov]

What happened?

When connecting the AWS Terraform MCP server, it fails to run with uvx command:

$ docker exec -it LibreChat-API /bin/sh
/app/api # uvx awslabs.terraform-mcp-server@latest
  x No solution found when resolving tool dependencies:
  `-> Because only the following versions of playwright are available:
          playwright<=1.40.0
          playwright==1.41.0
          playwright==1.41.1
          playwright==1.41.2
          playwright==1.42.0
          playwright==1.43.0
          playwright==1.44.0
          playwright==1.45.0
          playwright==1.45.1
          playwright==1.46.0
          playwright==1.47.0
          playwright==1.48.0
          playwright==1.49.0
          playwright==1.49.1
          playwright==1.50.0
          playwright==1.51.0
          playwright==1.52.0
      and playwright>=1.40.0 has no wheels with a matching platform tag (e.g., `linux_x86_64`), we can conclude that playwright>=1.40.0 cannot be used.
      And because all versions of awslabs-terraform-mcp-server depend on playwright>=1.40.0 and you require awslabs-terraform-mcp-server, we can conclude that your requirements are
      unsatisfiable.

      hint: Wheels are available for `playwright` (v1.52.0) on the following platforms: `manylinux_2_17_aarch64`, `manylinux1_x86_64`, `manylinux2014_aarch64`, `macosx_10_13_x86_64`,
      `macosx_11_0_arm64`, `macosx_11_0_universal2`, `win32`, `win_amd64`, `win_arm64`
/app/api #

Version Information

$ docker images | grep -i LibreChat
ghcr.io/danny-avila/librechat-dev-api            latest          ec732384bd62   4 days ago      1.12GB
ghcr.io/danny-avila/librechat-rag-api-dev-lite   latest          e7da8e6aca0f   4 weeks ago     1.31GB

$ git rev-parse HEAD
dff4fcac00939cf5a9b2077eba4cadcfe47c72eb

Steps to Reproduce

1. Run latest dev version of Librechat.ai in Docker on x86_64 server.
2. Get into the Librechat-AI container shell: docker exec -it LibreChat-API /bin/sh
3. Try to run AWS Terraform MCP server with this command: uvx awslabs.terraform-mcp-server@latest

What browsers are you seeing the problem on?

No response

Relevant log output

from the error log:


{"code":-32000,"level":"error","message":"[MCP][awslabs.terraform-mcp-server] Connection failed: MCP error -32000: Connection closed","name":"McpError","stack":"McpError: MCP error -32000: Connection closed\n    at gn._onclose (/app/packages/mcp/dist/index.js:1:72153)\n    at _transport.onclose (/app/packages/mcp/dist/index.js:1:71622)\n    at ChildProcess.<anonymous> (/app/packages/mcp/dist/index.js:1:99136)\n    at ChildProcess.emit (node:events:524:28)\n    at maybeClose (node:internal/child_process:1104:16)\n    at ChildProcess._handle.onexit (node:internal/child_process:304:5)"}
{"code":-32000,"level":"error","message":"[MCP][awslabs.terraform-mcp-server] Connection failed: MCP error -32000: Connection closed","name":"McpError","stack":"McpError: MCP error -32000: Connection closed\n    at gn._onclose (/app/packages/mcp/dist/index.js:1:72153)\n    at _transport.onclose (/app/packages/mcp/dist/index.js:1:71622)\n    at ChildProcess.<anonymous> (/app/packages/mcp/dist/index.js:1:99136)\n    at ChildProcess.emit (node:events:524:28)\n    at maybeClose (node:internal/child_process:1104:16)\n    at ChildProcess._handle.onexit (node:internal/child_process:304:5)"}
{"code":-32000,"level":"error","message":"[MCP][awslabs.terraform-mcp-server] Connection failed: MCP error -32000: Connection closed","name":"McpError","stack":"McpError: MCP error -32000: Connection closed\n    at gn._onclose (/app/packages/mcp/dist/index.js:1:72153)\n    at _transport.onclose (/app/packages/mcp/dist/index.js:1:71622)\n    at ChildProcess.<anonymous> (/app/packages/mcp/dist/index.js:1:99136)\n    at ChildProcess.emit (node:events:524:28)\n    at maybeClose (node:internal/child_process:1104:16)\n    at ChildProcess._handle.onexit (node:internal/child_process:304:5)"}
{"code":-32000,"level":"error","message":"[MCP][awslabs.terraform-mcp-server] Failed to connect after 3 attempts MCP error -32000: Connection closed","name":"McpError","stack":"McpError: MCP error -32000: Connection closed\n    at gn._onclose (/app/packages/mcp/dist/index.js:1:72153)\n    at _transport.onclose (/app/packages/mcp/dist/index.js:1:71622)\n    at ChildProcess.<anonymous> (/app/packages/mcp/dist/index.js:1:99136)\n    at ChildProcess.emit (node:events:524:28)\n    at maybeClose (node:internal/child_process:1104:16)\n    at ChildProcess._handle.onexit (node:internal/child_process:304:5)"}
{"code":-32000,"level":"error","message":"[MCP][awslabs.terraform-mcp-server] Initialization failed MCP error -32000: Connection closed","name":"McpError","stack":"McpError: MCP error -32000: Connection closed\n    at gn._onclose (/app/packages/mcp/dist/index.js:1:72153)\n    at _transport.onclose (/app/packages/mcp/dist/index.js:1:71622)\n    at ChildProcess.<anonymous> (/app/packages/mcp/dist/index.js:1:99136)\n    at ChildProcess.emit (node:events:524:28)\n    at maybeClose (node:internal/child_process:1104:16)\n    at ChildProcess._handle.onexit (node:internal/child_process:304:5)"}

Screenshots

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[alexeygumirov]

I made a workaround for this MCP server:

• I run in via the Supergateway container, connected to the Librechat network.
• And I had to re-build Supergateway container locally, using Debian Bookworm Slim as a base, not Alpine (which Supergateway uses by default and which also does not work for this MCP server).

But, actually, if Librechat.ai would use Debain or Ubuntu as a base for its container - then we would not have issue with the platform tag. I am not insisting on this, because it is possibel to make a workaround. 😀

[alexeygumirov]

I created a repo with Dockerfiles to build Supergateway docker images based on Debian Bookworm Slim:
alexeygumirov/supergateway-docker-slim