Getting NPM error Prisma/engine on Docker build

[surfacenathan]

When i run docker build . in my directory, I get the following error

 > [4/7] RUN npm install --omit=dev:
50.00 npm notice
50.00 npm notice New major version of npm available! 9.5.1 -> 10.8.2
50.00 npm notice Changelog: <https://github.com/npm/cli/releases/tag/v10.8.2>
50.00 npm notice Run `npm install -g npm@10.8.2` to update!
50.00 npm notice
50.00 npm ERR! code 1
50.00 npm ERR! path /app/node_modules/@prisma/engines
50.00 npm ERR! command failed
50.00 npm ERR! command sh -c node scripts/postinstall.js
50.00 npm ERR! node:internal/process/promises:288
50.00 npm ERR!             triggerUncaughtException(err, true /* fromPromise */);
50.00 npm ERR!             ^
50.00 npm ERR!
50.00 npm ERR! Error: aborted
50.00 npm ERR!     at connResetException (node:internal/errors:717:14)
50.00 npm ERR!     at TLSSocket.socketCloseListener (node:_http_client:462:19)
50.00 npm ERR!     at TLSSocket.emit (node:events:525:35)
50.00 npm ERR!     at node:net:322:12
50.00 npm ERR!     at TCP.done (node:_tls_wrap:588:7) {
50.00 npm ERR!   code: 'ECONNRESET',
50.00 npm ERR!   attemptNumber: 1,
50.00 npm ERR!   retriesLeft: 2
50.00 npm ERR! }
50.00 npm ERR!
50.00 npm ERR! Node.js v18.16.0
50.00
50.00 npm ERR! A complete log of this run can be found in:
50.00 npm ERR!     /root/.npm/_logs/2024-07-30T07_24_35_868Z-debug-0.log

I'm not using prisma as a database although I'm using it in shopify.server.js for session storage. 

  sessionStorage: new PrismaSessionStorage(prisma),

If anyone knows or can help. 

Here's my full docker file:

FROM node:18.16.0-alpine
ENV SCOPES=read_content,read_orders,read_shipping,write_orders,write_products
ENV SHOPIFY_API_KEY=
ENV SHOPIFY_API_SECRET=
WORKDIR /app
COPY . .
ENV NODE_ENV=production

RUN npm install --omit=dev
# Remove CLI packages since we don't need them in production by default.
# Remove this line if you want to run CLI commands in your container.
RUN npm remove @shopify/app @shopify/cli
RUN npm run build

CMD ["npm", "run", "docker-start"]

[21O]

Did you ever find the solution to this? I've got the same issue.