Invalid photon through Docker image

Hi,

I’m trying to deploy my working web-app including a backend with prisma2.

But when i start the docker image, an error appears with the first “photon.mytable” call: Invalid photon.() invocation in /usr/src/app/main.js Reason: Error occurred during query execution: ConnectorError(ConnectorError { user_facing_error: None, kind: QueryError(SqliteFailure(Error { code: Unknown, extended_code: 1 }, Some("no such table: dev.mytable"))

This behavior looks like i didn’t generated the schema, but i did in dockerfile:

FROM node:12.9.1-stretch
LABEL name="myapp-back" version="0.1.0"

WORKDIR /usr/src/app
COPY ./package.json package.json
COPY ./yarn.lock yarn.lock

RUN yarn install --frozen-lockfile --prod

COPY ./tsconfig.json tsconfig.json
COPY ./prisma/schema.prisma prisma/schema.prisma 
RUN yarn generate    <-- calls "prisma2 generate" in package.json

COPY ./src src
RUN yarn build

COPY ./src/schema.graphql ./dist/schema.graphql

ENV NODE_ENV prod
EXPOSE 4000

CMD ["yarn", "start"]

Moreover, this backend works fine on my local machine (out of a Docker image).

For info, schema.prisma starts with:

generator photon {
  provider      = "photonjs"
  binaryTargets = ["native", "debian-openssl-1.1.x"]
}

datasource db {
  provider = "sqlite"
  url      = "file:dev.db"
}

Any idea ?

[jean-noelp]

Thanks, it works! 😃

The entire solution: 1- think to backup prisma/migrations at the initial state with prisma2 lift save 2- use this Dockerfile:

FROM node:12.9.1-stretch
LABEL name="myapp-back" version="0.1.0"

WORKDIR /usr/src/app
COPY ./package.json package.json
COPY ./yarn.lock yarn.lock

RUN yarn install --frozen-lockfile --prod

COPY ./prisma/schema.prisma prisma/schema.prisma 
COPY ./prisma/migrations prisma/migrations.
RUN yarn generate        <-- prisma2 generate
RUN yarn dbintro           <-- prisma2 lift up --auto-approve

COPY ./tsconfig.json tsconfig.json
COPY ./src src
RUN yarn build

COPY ./src/schema.graphql ./dist/schema.graphql

ENV NODE_ENV production
EXPOSE 4000

CMD ["yarn", "start"]

Be careful: this is a versatile server: each time you will reload your image, the database will be reset! Think to use an external image/service to keep data.

[malekjaroslav]

try prisma2 lift up --auto-approve