fix(backend-image): keep bcrypt native addon in runtime stage
The runtime stage reinstalled deps with `npm ci --ignore-scripts`, which skips
bcrypt's install script and never produces bcrypt_lib.node. The app then
crash-looped at runtime ("Cannot find module .../bcrypt_lib.node") — the Prisma
seed and NestJS auth both require bcrypt — so nginx returned 502 on login.
Reuse the builder's node_modules (bcrypt built WITH scripts + generated Prisma
client) instead of reinstalling. builder and runtime share node:20-slim, so the
native binaries are ABI/platform-compatible.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 4.8
parent
c0f61166a0
commit
a056cefa76
@@ -29,9 +29,13 @@ COPY backend/package.json ./backend/
|
|||||||
COPY frontend/package.json ./frontend/
|
COPY frontend/package.json ./frontend/
|
||||||
COPY backend/prisma ./backend/prisma
|
COPY backend/prisma ./backend/prisma
|
||||||
|
|
||||||
RUN npm ci --ignore-scripts
|
# Reuse the builder's node_modules: it already contains bcrypt's compiled
|
||||||
|
# native addon (built WITH install scripts) and the generated Prisma client.
|
||||||
RUN cd backend && npx prisma generate
|
# A fresh `npm ci --ignore-scripts` here omits bcrypt's *.node binary, so the
|
||||||
|
# app crash-loops at runtime ("Cannot find module .../bcrypt_lib.node") — both
|
||||||
|
# the seed and NestJS auth require bcrypt. builder and runtime share the same
|
||||||
|
# node:20-slim base, so the native binaries are ABI/platform-compatible.
|
||||||
|
COPY --from=builder /app/node_modules ./node_modules
|
||||||
|
|
||||||
COPY --from=builder /app/backend/dist ./backend/dist
|
COPY --from=builder /app/backend/dist ./backend/dist
|
||||||
COPY backend/entrypoint.sh /entrypoint.sh
|
COPY backend/entrypoint.sh /entrypoint.sh
|
||||||
|
|||||||
Reference in New Issue
Block a user