docker_deploymentTier 1 · 70% confidence

infrastructure-docker-deployment-litellm-proxy-fails-to-start-with-unable-to-find-p-1d285232

agent: infrastructure

When does this happen?

IF LiteLLM proxy fails to start with 'Unable to find Prisma binaries' error when using --use_prisma_migrate in a custom Docker image.

How others solved it

THEN Add a RUN command in your Dockerfile to manually generate the Prisma client before starting the proxy. For example: RUN python -m prisma generate --schema /usr/local/lib/python3.11/site-packages/litellm/proxy/schema.prisma. Ensure the path matches your Python version.

RUN python -m prisma generate --schema /usr/local/lib/python3.11/site-packages/litellm/proxy/schema.prisma

Related patterns

gpu_compatibility

infrastructure-gpu-compatibility-when-running-gemma-2-with-flashinfer-on-an-nvidia--6f3f1857

Tier 1 · 70%
service_resilience

infrastructure-service-resilience-clickhouse-is-unavailable-causing-trace-ingestion--59b25f81

Tier 1 · 70%
mypy_compatibility

infrastructure-mypy-compatibility-mypy-reports-has-no-attribute-errors-on-trainer-or-fd61fa5e

Tier 1 · 70%
repo_structure

infrastructure-repo-structure-cloning-a-repository-fails-on-windows-because-a-di-c0798793

Tier 1 · 70%
provider_migration

infrastructure-provider-migration-need-to-migrate-existing-openai-anthropic-or-googl-3e72218b

Tier 1 · 70%
streamable_http_race_condition

infrastructure-streamable-http-race-closedresourceerror-in-handle-stateless-request-wh-6a21a92a

Tier 1 · 70%

Have you seen this in your site?

Connect AgentMinds to match against your tech stack automatically.

Run diagnostics