Prisma migration issue on BlitzJS project

[jaaouany (Jaaouani)]

Hi,
I’m having issues with prisma, when specifying the DATABASE_URL to the internal built-in variable, I get a can’t reach database error, from dockerfile and when using buildpack.
The database is set on private.

a random dockerfile to test

FROM node:16-alpine
ARG DATABASE_URL
ARG SESSION_SECRET
WORKDIR /app
ENV DATABASE_URL=${DATABASE_URL}
ENV SESSION_SECRET=${SESSION_SECRET}
COPY . .
RUN npm install --legacy-peer-deps
RUN npx prisma migrate deploy
EXPOSE 3000
CMD ["npm", "run", "start"]

[rophilogene (Romaric Philogene)]

Hi @jaaouany ,

You can take a look at this thread since it’s related.

Unable to use environment vars inside dockerfile during build time

Hello @r4881t, Sadly, you cannot reach your cluster/database/services that run in your environment during the build phase of your application (unless public). Our builder that execute the Dockerfile are not in the same network than your environment, so it has no access/reach to databases. When doing RUN npm run migrate, this command will be executed during the build ;( If you want to run this command, you need to execute it during the start of your container application. So must be put insid…

In a nutshell , you can’t run RUN npx prisma migrate deploy since it’s executed at the build time of your container and the build process does not have access to your database. I would recommend using an entrypoint.sh and executing the migrate command before that your node process starts. You can take a look at this guide.

How to run commands before the application starts | Qovery