Are you using M1 Mac? If yes, then this is related to #8478

You can try adding openssl once though in the image by adding RUN apk update && apk add nodejs npm openssl python g++ make && rm -rf /var/cache/apk/*, otherwise I will suggest you to use node:18-slim image.

Hi @Story27 👋

In your docker file, you are generating the Prisma client multiple times. This is unnecessary and can be optimized. You should generate the Prisma client only once during the build stage. You should also ensure that the node_modules directory is correctly copied from the builder stage to the runner stage. Try out this revised docker file:

FROM node:20-alpine AS base

# Install dependencies only when needed
FROM base AS deps
RUN apk add --no-cache libc6-compat g++ python3 openjdk11
WORKDIR /app

# Install dependencies
COPY package.json package-lock.json* ./
RUN npm ci

# Rebuild the source code only when needed
FROM base AS builder
WORKDIR /app
COPY --from=deps /app/node_modules ./node_modules
COPY --from=deps /app/package-lock.json ./package-lock.json
COPY . .
COPY prisma ./prisma

ENV NEXT_TELEMETRY_DISABLED 1

# Generate Prisma client
RUN npx prisma generate --schema=./prisma/schema.prisma

RUN npm run build

# Production image, copy all the files and run next
FROM base AS runner
WORKDIR /app

# Install g++ in the runner stage
RUN apk add --no-cache g++

ENV NODE_ENV production
# Uncomment the following line in case you want to disable telemetry during runtime.
# ENV NEXT_TELEMETRY_DISABLED 1

RUN addgroup --system --gid 1001 nodejs
RUN adduser --system --uid 1001 nextjs

COPY --from=builder /app/public ./public

# Set the correct permission for prerender cache
RUN mkdir .next
RUN chown nextjs:nodejs .next

# Create necessary directories and set permissions
RUN mkdir -p /app/Executed-codes/codes /app/Executed-codes/outputs /app/Executed-codes/inputs
RUN chown -R nextjs:nodejs /app/Executed-codes

# Automatically leverage output traces to reduce image size
# https://nextjs.org/docs/advanced-features/output-file-tracing
COPY --from=builder --chown=nextjs:nodejs /app/.next/standalone ./
COPY --from=builder --chown=nextjs:nodejs /app/.next/static ./.next/static

# Copy Prisma files
COPY --from=builder /app/prisma ./prisma
COPY --from=builder /app/node_modules/.prisma ./node_modules/.prisma
COPY --from=builder /app/node_modules/@prisma ./node_modules/@prisma

USER nextjs

EXPOSE 3000

ENV PORT 3000
ENV HOSTNAME "0.0.0.0"

# server.js is created by next build from the standalone output
# https://nextjs.org/docs/pages/api-reference/next-config-js/output
CMD ["node", "server.js"]

There is no prismagraphql/prisma:2 image available on the docker hub.

On this github issue they say that:

We are releasing Prisma 2 as a library rather than a server. So you will use it as just another dependency for your application. So you will create a docker image just like for another node app

This open issue might help and this recent tutorial to build a docker image using prisma 2 should help you too.

The last part of my Dockerfile is:

#CMD ["yarn", "start"] #commented out
CMD ["bin/startup.sh"]

I no longer do yarn start. Instead I call a script and inside I do the stuff I need:

# --- bin/startup.sh ---

npx prisma generate
npx prisma migrate deploy
yarn start