Prisma•4mo ago

Build failure because of prisma?

See image

14 Replies

"Step #0 - "Build": npm warn exec The following package was not found and will be installed: [email protected]" makes no sense @kappa.ai @RaphaelEtim Do you think you can give me a hand with this?

RaphaelEtim•4mo ago

Hi @laphatize, can you please provide some more context? Can you provide the docker file, schema and any other relevant information?

laphatize•4mo ago

Hi, Raphael. I think this issue was happening because of a new version of alpine:latest that was pushed. This works

# Specify the base image
FROM  node:lts-alpine3.20


# Set the working directory
WORKDIR /app

# Copy package.json and yarn.lock to the container
COPY package.json yarn.lock ./

# generated prisma files
COPY prisma ./prisma/

# Copy the rest of the application files to the container
COPY . .

# Copy the .env file to the container
#COPY .env ./

# Install dependencies
RUN yarn install

# Generate Prisma Client code
RUN npx prisma generate

EXPOSE 3000

# Start the application

CMD ["yarn", "start"]

# Specify the base image
FROM  node:lts-alpine3.20


# Set the working directory
WORKDIR /app

# Copy package.json and yarn.lock to the container
COPY package.json yarn.lock ./

# generated prisma files
COPY prisma ./prisma/

# Copy the rest of the application files to the container
COPY . .

# Copy the .env file to the container
#COPY .env ./

# Install dependencies
RUN yarn install

# Generate Prisma Client code
RUN npx prisma generate

EXPOSE 3000

# Start the application

CMD ["yarn", "start"]

This does not:

```
# Specify the base image
FROM  node:lts-alpine3.20


# Set the working directory
WORKDIR /app

# Copy package.json and yarn.lock to the container
COPY package.json yarn.lock ./

# generated prisma files
COPY prisma ./prisma/

# Copy the rest of the application files to the container
COPY . .

# Copy the .env file to the container
#COPY .env ./

# Install dependencies
RUN yarn install

# Generate Prisma Client code
RUN npx prisma generate

EXPOSE 3000

# Start the application

CMD ["yarn", "start"]

```
# Specify the base image
FROM  node:lts-alpine3.20


# Set the working directory
WORKDIR /app

# Copy package.json and yarn.lock to the container
COPY package.json yarn.lock ./

# generated prisma files
COPY prisma ./prisma/

# Copy the rest of the application files to the container
COPY . .

# Copy the .env file to the container
#COPY .env ./

# Install dependencies
RUN yarn install

# Generate Prisma Client code
RUN npx prisma generate

EXPOSE 3000

# Start the application

CMD ["yarn", "start"]

laphatize•4mo ago

Step #0 - "Build": Please try to install it by hand with yarn add @prisma/client and rerun npx "prisma generate" 🙏.

RaphaelEtim•4mo ago

Thanks for pointing that out.

Lord Zd•4mo ago

@laphatize I am having a similar issue with docker and prisma since the update ive read your working/non working dockerfiles and cant see any difference am i missing something?

Lord Zd•4mo ago

I am using node:20.15-alpine and getting the following error. I have confirmed its not a network issue however the circumstance is the same. Previous deployments still up and running using same version but if I try deploy them again I get the same error. What version did you get working?

laphatize•4mo ago

node:lts-alpine3.20 did the trick for me but ur error is unrelated to this whats ur docker file lookin like oh lol in my example they are not different i had node:alpine before that was all

Lord Zd•4mo ago

Im using docker compose its on 18 atm as I have been trying different node versions to see if I could find a working one

Lord Zd•4mo ago

This is the compose file i deployed a few days ago which worked

laphatize•4mo ago

yeah im not skilled enouugh to help u with this -- maybe make a new thread ur issue is def diff than mine ur error is network related mine was an issue with the latest version of alpine you are not using the latest version of alpine as it seems so u should be fine

Lord Zd•4mo ago

Okay cheers anyway Ill look into it further. Ive already confirmed its not a network error by pinging the registry

Gaming

Programming

Build failure because of prisma?