Yassin Kortam 72c8888563 fix(docker): bake prisma offline in the componentized migrations image (#35485) ... The migrations image ran `prisma migrate deploy` against a bake anchored in $HOME with no node in the runtime stage, so prisma-client-py fell through to nodeenv and tried to download a Node runtime on first start. In an egress-restricted cluster that fails outright, and under an arbitrary uid the uid-specific cache path is unreadable, so the job never applies a migration. Move the bake to /opt/prisma with world-readable modes, install node in the runtime stage, and pin PRISMA_BINARY_CACHE_DIR / PRISMA_CLI_PATH / PRISMA_OFFLINE_MODE so the migration entrypoint runs the cached CLI directly. This is the same treatment the root, non_root and database images already carry. Resolves LIT-4727		2026-08-01 14:12:31 -07:00
..
Dockerfile	fix(docker): bake prisma offline in the componentized migrations image (#35485)	2026-08-01 14:12:31 -07:00
run.py	feat: add componentized proxy deployment with gateway, backend, ui, and migrations (#27557)	2026-05-16 09:25:17 -07:00