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?
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:
After prisma loads, something is trying to reach
/prisma/sqlwhich 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
prismadirectory 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?