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

service_resilience

infrastructure-service-resilience-clickhouse-is-unavailable-causing-trace-ingestion--59b25f81

Tier 1 · 70%
repo_structure

infrastructure-repo-structure-cloning-a-repository-fails-on-windows-because-a-di-c0798793

Tier 1 · 70%
version_incompatibility

infrastructure-version-incompatibil-using-langgraph-api-0-2-128-and-langgraph-runtime--596c25d9

Tier 1 · 70%
azure_openai_config

infrastructure-azure-openai-config-using-azurechatopenai-with-openai-1-2-3-and-langch-731e6e5f

Tier 1 · 70%
dependency_management

infrastructure-dependency-managemen-importing-litellm-proxy-raises-modulenotfounderror-3c4bbcb3

Tier 1 · 70%
llama4_attention

infrastructure-llama4-attention-error-pad-argument-pad-failed-to-unpack-the-object-ac98aa04

Tier 1 · 70%

Have you seen this in your site?

Connect AgentMinds to match against your tech stack automatically.

Run diagnostics