LiteLLM / LiteLLM

LiteLLM Prisma migrations fail with non-root Docker image on Alpine-based distros

Fix LiteLLM proxy Prisma migration failure when running in non-root Docker container on Alpine/Wolfi-based images Includes evidence for LiteLLM troubleshooting demand.

Source-backed Last updated May 23, 2026 1 source Needs local verification

Category: LiteLLM
Error signature: Prisma migrations not applied with docker non_root image — Prisma warning: doesn't know which engines to download for Linux distro wolfi, falling back to debian builds
Quick fix: Compare the failing environment with a known working setup, then change one configuration value at a time.
Updated: May 23, 2026
Verification status: Source-backed
Evidence: 1 public source URL

Before you change production

This page includes public source URLs in the imported troubleshooting record. Compare those references with your version and environment before applying changes.

Reproduce the smallest failing action and save non-secret logs before changing configuration.
Check versions for LiteLLM, related SDKs, package managers, CI runners, and hosting providers.
Change one setting or dependency at a time, then rerun the same failing command or request.
Avoid destructive commands, credential rotation, billing changes, or security relaxations without a rollback plan.

What this error means

Prisma migrations not applied with docker non_root image — Prisma warning: doesn't know which engines to download for Linux distro wolfi, falling back to debian builds is a LiteLLM failure pattern reported for developers trying to fix litellm proxy prisma migration failure when running in non-root docker container on alpine/wolfi-based images. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

GitHub Issue #18851 on BerriAI/litellm (created 2026-01-09, 5 comments): Running LiteLLM proxy in non-root Docker image based on Alpine/Wolfi causes Prisma migrate deploy to fallback to debian-built engines with warnings. Database version works but UI migration fails. Affects self-hosted LiteLLM proxy deployments — operational blocker for teams using minimal Docker images. Maps to LiteLLM per approved category mapping.

Common causes

GitHub Issue #18851 on BerriAI/litellm (created 2026-01-09, 5 comments): Running LiteLLM proxy in non-root Docker image based on Alpine/Wolfi causes Prisma migrate deploy to fallback to debian-built engines with warnings. Database version works but UI migration fails. Affects self-hosted LiteLLM proxy deployments — operational blocker for teams using minimal Docker images. Maps to LiteLLM per approved category mapping.

Quick fixes

Confirm the exact error signature matches Prisma migrations not applied with docker non_root image — Prisma warning: doesn't know which engines to download for Linux distro wolfi, falling back to debian builds.
Check the LiteLLM account, local tool state, and provider configuration involved in the failing workflow.
Compare the failing environment with a known working setup, then change one configuration value at a time.

Platform/tool-specific checks

Verify the command, editor, extension, or API client that produced the error.
Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

Capture the exact error message and the command, editor action, or request that triggered it.
Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
Review the source evidence below and compare it with your environment.
Apply one change at a time and rerun the smallest failing action.
Keep the working fix documented for the team or deployment environment.

How to prevent it

Keep provider/tool configuration documented.
Record non-secret diagnostics such as tool version, provider name, model name, and command path.
Add a lightweight check before CI or production workflows depend on the tool.

Diagnostic flow for this page

Match Prisma migrations not applied with docker non_root image — Prisma warning: doesn't know which engines to download for Linux distro wolfi, falling back to debian builds exactly before applying the quick fix.
Compare the failing environment with LiteLLM versions, account scope, provider settings, and deployment context.
Check the listed common causes in order, starting with the cause that best matches your logs.
Use the evidence status below to decide whether to confirm against public sources or official documentation.
Apply one reversible change, rerun the smallest failing action, and keep rollback notes.

FAQ

What does Prisma migrations not applied with docker non_root image — Prisma warning: doesn't know which engines to download for Linux distro wolfi, falling back to debian builds mean in LiteLLM?

Prisma migrations not applied with docker non_root image — Prisma warning: doesn't know which engines to download for Linux distro wolfi, falling back to debian builds indicates the workflow described by "LiteLLM Prisma migrations fail with non-root Docker image on Alpine-based distros" failed in a LiteLLM context. Start by confirming the exact signature and the component that emitted it.

What should I check first for Prisma migrations not applied with docker non_root image — Prisma warning: doesn't know which engines to download for Linux distro wolfi, falling back to debian builds?

Check whether this cause matches your environment: GitHub Issue #18851 on BerriAI/litellm (created 2026-01-09, 5 comments): Running LiteLLM proxy in non-root Docker image based on Alpine/Wolfi causes Prisma migrate deploy to fallback to debian-built engines with warnings. Database version works but UI migration fails. Affects self-hosted LiteLLM proxy deployments — operational blocker for teams using minimal Docker images. Maps to LiteLLM per approved category mapping.

Is the Prisma migrations not applied with docker non_root image — Prisma warning: doesn't know which engines to download for Linux distro wolfi, falling back to debian builds guidance source-backed?

The "LiteLLM Prisma migrations fail with non-root Docker image on Alpine-based distros" page is labeled source-backed. It has 1 public source URL from github.com, so use that evidence status when deciding how much additional verification you need.

When should I avoid the quick fix for Prisma migrations not applied with docker non_root image — Prisma warning: doesn't know which engines to download for Linux distro wolfi, falling back to debian builds?

For "LiteLLM Prisma migrations fail with non-root Docker image on Alpine-based distros", avoid applying "Compare the failing environment with a known working setup, then change one configuration value at a time." when the error text differs, the affected version or provider is different, or the change would touch credentials, billing, DNS, production deploy settings, or irreversible data.

What should I collect before debugging Prisma migrations not applied with docker non_root image — Prisma warning: doesn't know which engines to download for Linux distro wolfi, falling back to debian builds?

For "LiteLLM Prisma migrations fail with non-root Docker image on Alpine-based distros", collect the failing LiteLLM command or request, non-secret configuration, versions, timestamps, request IDs when available, and the smallest reproduction that still triggers the signature.