### Check for existing issues

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

### What happened?

## Description

Upgrading LiteLLM from `1.84.0` to `1.92.1` using the official `litellm-non_root` image causes Prisma migrations to fail before any database migration is executed.

The same Kubernetes deployment and database work correctly with LiteLLM `1.84.0`.

With `1.92.1`, LiteLLM finds the bundled Prisma CLI, detects the Wolfi distribution, falls back to Debian engines, and then attempts to write into:

```text /app/.cache/prisma-python/binaries/node_modules/@prisma/engines ```

This directory is not writable by the default user configured in the official non-root image.

## Upgrade

```text Previous version: 1.84.0 Affected version: 1.92.1 Image variant: litellm-non_root Deployment platform: Kubernetes ```

## Error

```text Running prisma migrate deploy

Using cached Prisma CLI at: /app/.cache/prisma-python/binaries/node_modules/.bin/prisma

prisma:warn Prisma doesn't know which engines to download for the Linux distro "wolfi". Falling back to Prisma engines built "debian".

Error: Can't write to /app/.cache/prisma-python/binaries/node_…