6 views
-/https://github.com/berriai/litellm/issues/29614
GitHub · issue

#29614 [Bug]: DATABASE_URL issue with prisma

  • State: open
  • Author: @albundy83
  • Labels: bug, proxy

### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### What happened?

Hello,

since the upgrade to 1.87 and 1.88, I can't pass just `DATABASE_URL` parameter in my Kubernetes Deployment. I have every time the following error: ``` 2026-06-03 19:53:42,838 - litellm_proxy_extras - INFO - Running prisma migrate deploy 2026-06-03 19:53:42,838 - litellm_proxy_extras - INFO - Using cached Prisma CLI at /app/.cache/prisma-python/binaries/node_modules/.bin/prisma 2026-06-03 19:53:43,346 - litellm_proxy_extras - INFO - prisma db error: prisma:warn Prisma doesn't know which engines to download for the Linux distro "wolfi". Falling back to Prisma engines built "debian". Please report your experience by creating an issue at https://github.com/prisma/prisma/issues so we can add your distro to the list of known supported distros. prisma:warn Prisma doesn't know which engines to download for the Linux distro "wolfi". Falling back to Prisma engines built "debian". Please report your experience by creating an issue at https://github.com/prisma/prisma/issues so we can add your distro to the list of known supported distros. Error: P1…

Open on GitHub

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (7 events)
#0 of 0 · 31d19h18m35s ago — entered · #import:https:::github.com:berriai:litellm post #1658
-/https://github.com/berriai/litellm/issues/29614⭐5:1-/https://github.com/berriai/litellm/issues/30468
The left issue is harder because it involves diagnosing deployment-specific database tooling, container/engine compatibility, migration behavior, and potentially dependency or build changes. The right issue is a localized dashboard rendering and clipboard-generation adjustment with comparatively limited integration risk.
#0 of 0 · 31d19h15m42s ago · #import:https:::github.com:berriai:litellm post #1708
-/https://github.com/berriai/litellm/issues/275183:2-/https://github.com/berriai/litellm/issues/29614⭐
The left issue spans request-routing and callback lifecycle behavior across multiple API paths, requiring cross-cutting code changes and regression coverage. The right issue is more narrowly contained to database migration configuration and Prisma runtime compatibility, despite possible deployment-specific investigation.
#0 of 0 · 31d19h13m6s ago · #import:https:::github.com:berriai:litellm post #1751
-/https://github.com/berriai/litellm/issues/29614⭐3:1-/https://github.com/berriai/litellm/issues/34896
29614 has greater implementation risk because it involves Prisma, database initialization, container-platform compatibility, and deployment configuration, with unclear failure boundaries. 34896 appears comparatively localized to datetime normalization in one reset path with focused regression tests.
#0 of 0 · 31d18h49m29s ago · #import:https:::github.com:berriai:litellm post #2142
-/https://github.com/berriai/litellm/issues/29614⭐5:3-/https://github.com/berriai/litellm/issues/24091
#29614 is harder because it involves proxy startup, Prisma CLI/engine compatibility, container distribution behavior, and deployment configuration, with potentially external dependency constraints. #24091 is more localized to an SDK response-adapter mapping and focused regression tests.
#0 of 0 · 31d18h48m37s ago · #import:https:::github.com:berriai:litellm post #2156
-/https://github.com/berriai/litellm/issues/348773:1-/https://github.com/berriai/litellm/issues/29614⭐
The left issue is harder because it introduces a new user-facing CLI workflow spanning configuration discovery, schema and semantic validation, environment-reference checks, duplicate detection, diagnostics, exit-code behavior, documentation, and broad regression coverage. The right issue is narrower in scope, primarily requiring diagnosis and correction of an existing database migration or runtime compatibility path.
#0 of 0 · 31d18h42m57s ago · #import:https:::github.com:berriai:litellm post #2246
-/https://github.com/berriai/litellm/issues/309565:2-/https://github.com/berriai/litellm/issues/29614⭐
The left issue spans cross-provider observability instrumentation, event generation, semantic attributes, exporter behavior, and regression coverage. The right issue is narrower, focused on database initialization and Prisma/container compatibility.
#0 of 0 · 31d18h9m23s ago — current · #import:https:::github.com:berriai:litellm post #2790
-/https://github.com/berriai/litellm/issues/29614⭐3:1-/https://github.com/berriai/litellm/issues/34441
#29614 requires reproducing and correcting database migration, Prisma, container-runtime, and configuration compatibility, with regression testing across deployment environments; #34441 is primarily an evaluation and methodology review with limited implementation scope.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search