Utilizing Prisma, Docker, and NextJS: The mystery of "npx prisma db push" within docker-compose

Question

Utilizing Prisma, Docker, and NextJS: The mystery of "npx prisma db push" within docker-compose

I am looking to containerize my application (Prisma 4.9.1, NextJS 12, PostgreSQL) using Docker. The goal is to make it easy for users to clone the repository, type docker-compose up, and have everything running smoothly.

The issue I am facing is determining where to place the command npx prisma db push. I have tried various locations without success. Any suggestions or ideas?

My Dockerfile:

FROM node:18 AS dependencies

WORKDIR /app
COPY package.json yarn.lock ./
RUN yarn

FROM node:18 AS build

WORKDIR /app
COPY --from=dependencies /app/node_modules ./node_modules
COPY . .

RUN npx prisma generate
RUN yarn build:in:docker

FROM node:18 AS deploy

WORKDIR /app

ENV NODE_ENV production

COPY --from=build /app/public ./public
COPY --from=build /app/package.json ./package.json
COPY --from=build /app/.next/standalone ./
COPY --from=build /app/.next/static ./.next/static
COPY --from=build /app/node_modules ./node_modules
COPY --from=build /app/prisma ./prisma

EXPOSE 3000

ENV PORT 3000

CMD ["node", "server.js"]

My docker-compose.yml file:

version: '3.9'
services:
  postgres:
    image: postgres:latest
    container_name: postgres
    hostname: myhost
    ports:
      - 5432:5432
    environment:
      POSTGRES_USER: root
      POSTGRES_PASSWORD: password
      POSTGRES_DB: splitmate
    volumes:
      - postgres-data:/var/lib/postgresql/data
    restart: unless-stopped
  splitmate-app:
    image: splitmate
    build:
      context: .
      dockerfile: Dockerfile
      target: deploy
    volumes:
      - postgres-data:/app/postgres-data
    environment:
      DATABASE_URL: postgresql://root:password@myhost:5432/splitmate?schema=public&connect_timeout=60
    ports:
      - 3000:3000
volumes:
  postgres-data:

The container builds successfully and starts. However, when the code attempts to access the database, I encounter the following error:

features-splitmate-app-1  | Invalid `prisma.account.findUnique()` invocation:
features-splitmate-app-1  | 
features-splitmate-app-1  | 
features-splitmate-app-1  | The table `public.Account` does not exist in the current database. {
features-splitmate-app-1  |   message: '\n' +
features-splitmate-app-1  |     'Invalid `prisma.account.findUnique()` invocation:\n' +
features-splitmate-app-1  |     '\n' +
features-splitmate-app-1  |     '\n' +
features-splitmate-app-1  |     'The table `public.Account` does not exist in the current database.',
features-splitmate-app-1  |   stack: 'Error: \n' +
features-splitmate-app-1  |     'Invalid `prisma.account.findUnique()` invocation:\n' +
features-splitmate-app-1  |     '\n' +
features-splitmate-app-1  |     '\n' +
features-splitmate-app-1  |     'The table `public.Account` does not exist in the current database.\n' +
features-splitmate-app-1  |     '    at RequestHandler.handleRequestError (/app/node_modules/@prisma/client/runtime/index.js:31941:13)\n' +
features-splitmate-app-1  |     '    at RequestHandler.handleAndLogRequestError (/app/node_modules/@prisma/client/runtime/index.js:31913:12)\n' +
features-splitmate-app-1  |     '    at RequestHandler.request (/app/node_modules/@prisma/client/runtime/index.js:31908:12)\n' +
features-splitmate-app-1  |     '    at async PrismaClient._request (/app/node_modules/@prisma/client/runtime/index.js:32994:16)\n' +
features-splitmate-app-1  |     '    at async getUserByAccount (/app/node_modules/@next-auth/prisma-adapter/dist/index.js:11:29)',
features-splitmate-app-1  |   name: 'Error'
features-splitmate-app-1  | }

docker next.js prisma

Answer 1

Answer №1

I successfully resolved the issue

Updated Dockerfile:

FROM node:18 AS dependencies

WORKDIR /app
COPY package.json yarn.lock ./
RUN yarn

FROM node:18 AS build

WORKDIR /app
COPY --from=dependencies /app/node_modules ./node_modules
COPY . .

RUN npx prisma generate
RUN yarn build:in:docker
COPY migrate-and-start.sh .
RUN chmod +x migrate-and-start.sh

FROM node:18 AS deploy

WORKDIR /app

ENV NODE_ENV production

COPY --from=build /app/public ./public
COPY --from=build /app/package.json ./package.json
COPY --from=build /app/.next/standalone ./
COPY --from=build /app/.next/static ./.next/static
COPY --from=build /app/node_modules ./node_modules
COPY --from=build /app/prisma ./prisma
COPY --from=build /app/migrate-and-start.sh .

EXPOSE 3000

ENV PORT 3000

CMD ["./migrate-and-start.sh"]

migrate-and-start.sh

#!/bin/bash

npx prisma generate
npx prisma db push
node server.js

Adjusted docker-compose.yml

version: '3.9'
services:
  postgres:
    image: postgres:latest
    container_name: postgres
    hostname: myhost
    ports:
      - 5432:5432
    environment:
      POSTGRES_USER: root
      POSTGRES_PASSWORD: password
      POSTGRES_DB: splitmate
    volumes:
      - postgres-data:/var/lib/postgresql/data
    restart: unless-stopped
  splitmate-app:
    image: splitmate
    build:
      context: .
      dockerfile: Dockerfile
      target: deploy
    volumes:
      - postgres-data:/app/postgres-data
    environment:
      DATABASE_URL: postgresql://root:password@myhost:5432/splitmate?schema=public&connect_timeout=60
    ports:
      - 3000:3000
volumes:
  postgres-data:

Answer 2

I successfully resolved the issue

Updated Dockerfile:

FROM node:18 AS dependencies

WORKDIR /app
COPY package.json yarn.lock ./
RUN yarn

FROM node:18 AS build

WORKDIR /app
COPY --from=dependencies /app/node_modules ./node_modules
COPY . .

RUN npx prisma generate
RUN yarn build:in:docker
COPY migrate-and-start.sh .
RUN chmod +x migrate-and-start.sh

FROM node:18 AS deploy

WORKDIR /app

ENV NODE_ENV production

COPY --from=build /app/public ./public
COPY --from=build /app/package.json ./package.json
COPY --from=build /app/.next/standalone ./
COPY --from=build /app/.next/static ./.next/static
COPY --from=build /app/node_modules ./node_modules
COPY --from=build /app/prisma ./prisma
COPY --from=build /app/migrate-and-start.sh .

EXPOSE 3000

ENV PORT 3000

CMD ["./migrate-and-start.sh"]

migrate-and-start.sh

#!/bin/bash

npx prisma generate
npx prisma db push
node server.js

Adjusted docker-compose.yml

version: '3.9'
services:
  postgres:
    image: postgres:latest
    container_name: postgres
    hostname: myhost
    ports:
      - 5432:5432
    environment:
      POSTGRES_USER: root
      POSTGRES_PASSWORD: password
      POSTGRES_DB: splitmate
    volumes:
      - postgres-data:/var/lib/postgresql/data
    restart: unless-stopped
  splitmate-app:
    image: splitmate
    build:
      context: .
      dockerfile: Dockerfile
      target: deploy
    volumes:
      - postgres-data:/app/postgres-data
    environment:
      DATABASE_URL: postgresql://root:password@myhost:5432/splitmate?schema=public&connect_timeout=60
    ports:
      - 3000:3000
volumes:
  postgres-data:

Answer 3

Answer №2

After some searching, I came across a solution that closely resembles this approach:

Docker Configuration

FROM node:18-alpine

# Set working directory
WORKDIR /app

# Copy project files
COPY . .

# Update npm to latest version
RUN npm install -g npm@latest

# Install project dependencies
RUN npm install

# Expose port 3000
EXPOSE 3000

# Start the application
CMD source migrate-and-start.sh

migrate-and-start.sh

#!/bin/sh
npm run build
npx prisma generate
npx prisma migrate dev --name init
npm run start

This setup specifically addresses issues where Prisma fails to locate a ready PostgreSQL database.

Answer 4

After some searching, I came across a solution that closely resembles this approach:

Docker Configuration

FROM node:18-alpine

# Set working directory
WORKDIR /app

# Copy project files
COPY . .

# Update npm to latest version
RUN npm install -g npm@latest

# Install project dependencies
RUN npm install

# Expose port 3000
EXPOSE 3000

# Start the application
CMD source migrate-and-start.sh

migrate-and-start.sh

#!/bin/sh
npm run build
npx prisma generate
npx prisma migrate dev --name init
npm run start

This setup specifically addresses issues where Prisma fails to locate a ready PostgreSQL database.

Utilizing Prisma, Docker, and NextJS: The mystery of "npx prisma db push" within docker-compose

Answer №1

Answer №2

Similar questions

Prevent Next.js 13 from caching Firebase response or query result

Is a loading screen necessary when setting up the Stripe API for the checkout session?

Having Trouble with CORS when Sending a POST Request to Next.js 13.4.4 API Endpoint

Is it possible to modify the default case sensitivity of Next.js routes to make them case insensitive?

Using RSelenium and Docker containers to extract data (leveraging makeFirefoxProfile and mime types)

Issue with state update in Markdown Editor using React and Next.js

Is it possible to customize the naming of the many-to-many tables in Next.js with Prisma?

Parsing XLSX files using next.js on an API route from an incoming request

Error in Typescript: An element is implicitly assigned the 'any' type because a string expression is being used to index a different type

Troubleshooting NextJS useEffect with localStorage

Operating multiple containers with kubernetes for job processing

Is there a way to toggle the visibility of all React components while a loading screen is being displayed?

A guide to organizing page components across multiple `/pages` directories in a Next.js application

The flow of execution context does not transition smoothly from getStaticPaths to getStaticProps as expected

Invalid default value for Drizzle timestamp at current date and time

Prisma unexpectedly updates the main SQL Server database instead of the specified database in the connection string

Struggling to successfully upload a file to the Strapi upload API from a Next.js API route

Leveraging NextJS and React's Context API by incorporating a layout component wrapper

Struggling with importing aliases in TypeScript for shadcn-ui library

Ways to abbreviate a URL using Next JS