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

#26097 [Bug]: Self-hosted installation fail due to schema.prisma

  • State: open
  • Author: @Sly777
  • Labels: bug, SDK

### Check for existing issues

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

### What happened?

While trying to do a basic install of LiteLLM the script fails due to the command prisma generate not being permitted.

You can also check all details on this issue in different repo: https://github.com/community-scripts/ProxmoxVE/issues/13854

### Steps to Reproduce

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/litellm.sh)"

### Relevant log output

```shell Installing Prisma CLI {'x86': False, 'risc': False, 'lts': False}

Install prebuilt node (25.9.0) ../opt/litellm/.venv/lib/python3.13/site-packages/nodeenv.py:639: DeprecationWarning: Python 3.14 will, by default, filter extracted tar archives and reject files or modify their metadata. Use the filter argument to control this behavior. archive.extractall(src_dir, extract_list) ... done. Error: Could not find Prisma Schema that is required for this command. You can either provide it with --schema argument, set it as prisma.schema in your package.json or put it into the default location. Checked following paths: schema.prisma: file not found p…

GitHub resolver

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

Refresh page
vote history (3 events)
#0 of 0 · 31d18h20m41s ago — entered · #import:https:::github.com:berriai:litellm post #2714
The right-hand task requires broader provider-specific compatibility logic, regression analysis, and comprehensive testing across model variants and failure paths, while the left is a narrower installation and packaging configuration fix.
The left issue requires changes across request translation rules, compatibility handling, and regression coverage for multiple tool categories and provider behaviors. The right issue is narrower, centered on packaging or installation configuration and validation of the deployment path.
#0 of 0 · 31d17h51m41s ago — current · #import:https:::github.com:berriai:litellm post #3222
The right-hand task is harder because it involves packaging, dependency generation, installation tooling, and environment-specific compatibility, creating broader reproduction and regression risk. The left-hand task is comparatively localized to dashboard data filtering and permission-aware presentation.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search