Skip to content

MCP servers: (finch build failures with UV_PYTHON_PREFERENCE=only-system) #270

@rickosaws

Description

@rickosaws

Describe the bug

When using finch build -t awslabs/aws-documentation-mcp-server . the aws-documentation-mcp-server fails with missing interpreter error during the build phase.

[uv 6/7] RUN --mount=type=cache,target=/root/.cache/uv uv sync --frozen --no-dev --no-editable:
0.133 error: No interpreter found for Python 3.10 in search path

Expected Behavior

Container image should build successfully.

Current Behavior

Build fails with the following errors

[uv 6/7] RUN --mount=type=cache,target=/root/.cache/uv uv sync --frozen --no-dev --no-editable:
0.133 error: No interpreter found for Python 3.10 in search path

Reproduction Steps

Setting or leaving UV_PYTHON_PREFERENCE=only-system in the DockerFile and running finch build -t awslabs/aws-documentation-mcp-server .

Possible Solution

This can currently be worked around by setting UV_PYTHON_PREFERENCE=managed in the Dockerfile

Additional Information/Context

I am using finch instead of docker for my container build commands

OS

Mac OS 15.4.1

Server

aws-documentation-mcp-server

Server Version

No response

Region experiencing the issue

all

Other information

No response

Service quota

  • I have reviewed the service quotas for this construct

Metadata

Metadata

Assignees

Labels

awaiting-user-feedbackA reply has been given. Awaiting user feedback before moving onbacklogan accumulation of something, especially uncompleted work or matters that need to be dealt with.bugSomething isn't workingcannot-reproduceThe issue cannot be reproduced, please help with a https://sscce.org/

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions