Fly deploy restart loop due to Prisma error

[zachfedor]

I'm trying to diagnose an issue I'm having with our deployment on Fly and having a hard time locating where to look to solve the problem. After a deploy, I'm getting this in my logs:

2025-04-17 11:54:59.390	Prisma schema loaded from prisma/schema.prisma
2025-04-17 11:55:00.189	Error: ENOENT: no such file or directory, scandir '/myapp/prisma/sql'
2025-04-17 11:55:00.750	ERROR: cannot exec: sync cmd: cannot run command: exit status 1

After prisma loads, something is trying to reach /prisma/sql which doesn't, and to my knowledge, shouldn't exist. The VM then restarts over and over till it reaches the max of 10 and then gives up.

I checked the Dockerfile and don't see any explicit mention of this file/directory other than copying the whole prisma directory to /myapp. I haven't changed any configuration or env variabless from the defaults.

Can anyone point me in the appropriate direction to debug this problem?

[kentcdodds]

If you deleted that directory because you're not using any SQL queries, then you need to remove the --sql flag from your Prisma commands. They appear in a couple of places.

epic-stack/other/litefs.yml

Line 44 in 4bee576

- cmd: npx prisma generate --sql

epic-stack/package.json

Line 20 in 4bee576

"setup": "npm run build && prisma migrate deploy && prisma generate --sql && playwright install",

epic-stack/.github/workflows/deploy.yml

Line 37 in 4bee576

run: npx prisma migrate deploy && npx prisma generate --sql

epic-stack/.github/workflows/deploy.yml

Line 64 in 4bee576

run: npx prisma migrate deploy && npx prisma generate --sql

[zachfedor]

Ah, thanks for the direction @kentcdodds !

For anyone else who might appear here from search results, this occurred from my recent update to a later version using the epicli update command. Specifically it was this commit. I'm not sure if I accidentally deleted the file when it was created by the update, but the relevant changes in other files also didn't appear in the list of patches. There was no other warning via the linter or typechecker because the non-patched files were still fine.

It's probably rare enough of a problem for other users who happened to upgrade from past versions similar to mine, but would adding a check in the Dockerfile to ensure the prisma/sql directory exists prevent this problem?