fix(docker): prevent pnpm TTY prompt when BuildKit cache has stale node_modules

pnpm 11 aborts with ERR_PNPM_ABORTED_REMOVE_MODULES_DIR_NO_TTY when it
detects an existing node_modules directory and there is no TTY to confirm
purging it. This happens in Portainer when BuildKit layer cache reuses a
prior deps stage containing node_modules.

- .npmrc: set confirmModulesPurge=false (skip prompt unconditionally)
- Dockerfile deps stage: set CI=true (belt-and-suspenders for pnpm CI mode)

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
2026-06-25 09:10:33 +02:00
parent b4067c7685
commit bdf53980c0
2 changed files with 2 additions and 0 deletions
+1
View File
@@ -3,3 +3,4 @@ onlyBuiltDependencies[]=core-js
onlyBuiltDependencies[]=prisma
onlyBuiltDependencies[]=sharp
onlyBuiltDependencies[]=unrs-resolver
confirmModulesPurge=false
+1
View File
@@ -6,6 +6,7 @@ RUN apk add --no-cache openssl && \
FROM base AS deps
WORKDIR /app
ENV PRISMA_CLI_BINARY_TARGETS=linux-musl-openssl-3.0.x
ENV CI=true
COPY .npmrc package.json pnpm-lock.yaml pnpm-workspace.yaml ./
RUN pnpm install --frozen-lockfile --ignore-scripts