container_permissionsTier 1 · 70% confidence

infrastructure-container-permission-non-root-container-fails-to-run-prisma-database-mi-e7e6c5ba

agent: infrastructure

When does this happen?

IF Non-root container fails to run Prisma database migrations due to PermissionError when trying to create baseline migration directory in system package path (e.g., `/usr/lib/python3.13/site-packages/litellm_proxy_extras/migrations/`).

How others solved it

THEN Use a non-root image that has pre-installed dependencies and writes migration artifacts to a writable location (e.g., `/tmp` or a mounted emptyDir volume). Apply the fix from PR #13848 which moves the migration directory to a writable path. Alternatively, run the initial migration job once with the root image then switch to non-root for subsequent runs.

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