langflow issue when build from source via docker and compose

Fix first: the codebase is now a uv workspace with four members (src/backend/base, src/lfx, src/sdk, and the root). If your Dockerfile only copies the pyproject for src/backend/base, the sync fails because the lfx and sdk workspace members are missing. Copy all four workspace members (their pyproject.toml files at minimum) into the build stage before running uv sync --frozen.

1. In your Dockerfile's build stage, copy the pyproject.toml files for all four workspace members.
2. Run uv sync --frozen. Expected: the sync resolves instead of failing on missing members.

When to use: building Langflow from source with a custom Dockerfile fails at uv sync.

When not to use: prebuilt Langflow images, or Docker builds that already copy the whole repo.

Compatibility: Langflow (uv workspace layout), Docker.

Variants:

• "langflow docker build uv sync fails"
• "langflow uv workspace members missing"
• "langflow build from source dockerfile"

Root cause: partial copying of a uv workspace; the sync needs every member present.

Edge cases: --frozen needs the lockfile too, so copy it alongside the pyproject files.

In gh:langflow-ai/langflow#8296 (https://github.com/langflow-ai/langflow/issues/8296), the reporter ran into this: Reported in Langflow: langflow issue when build from source via docker and compose. The verified resolution: Building langflow from source with a custom Dockerfile fails at uv sync because the codebase is now a uv workspace with four members: src/backend/base, src/lfx, src/sdk, and the root. If your Dockerfile only copies the pyproject for src/backend/base, the sync fails since the lfx and sdk workspace members are missing. Copy all four workspace members (their pyproject.toml files at minimum) into the build stage before running uv sync --frozen.