Forum

Hi Zeabur Team,

Our frontend service builds have been failing consistently for the past hour. The build fails at step [3/6] RUN npm update -g npm which is injected by Zeabur's build pipeline — this step is not in our Dockerfile.

Project ID: 698dc48967b6b3d51212e29f
Service ID: 698dc49367b6b3d51212e2a1
Failed Deployment: deployment-69c3fccbb34287b881669861
Branch: main

Error:

#7 [3/6] RUN npm update -g npm
#7 9.663 npm error code MODULE_NOT_FOUND
#7 9.663 npm error Cannot find module 'promise-retry'
#7 ERROR: process "/bin/sh -c npm update -g npm" did not complete successfully: exit code: 1

Key observations:

• Zeabur is using node:22 with WORKDIR /src, but our Dockerfile specifies node:20-alpine with WORKDIR /app — so our Dockerfile is being ignored
• The npm update -g npm step is not in our Dockerfile; it's injected by Zeabur's build system
• The promise-retry module is missing from the bundled npm in the Node 22 image
• Previous builds (54 minutes ago) deployed successfully, so this appears to be a recent regression in your build image

Could you please:

1. Fix the npm update -g npm step in your build pipeline, or
2. Allow our custom Dockerfile to be used instead of the auto-build pipeline

This is blocking our production deployments. Appreciate a quick resolution.

Thanks,
Suraj Kumar