Stuck in docker build if anything interrupts pnpm i

[isimmons]

At first I was getting the warning about node_modules will be deleted and reinstalled (Y/n) * true

Not sure what "true" is about and if I enter Y and hit enter it just seems stuck in a loop.

Now since v10.5.1 just released, I get the update available... run pnpm add -g pnpm to update message and it is just stuck there.

How do I deal with this in a docker image that is trying to build?

Is there a way to just ignore all of this and install my dependencies?

Here is my simple docker file that would have worked fine before v10 release. Never mind the stage naming and comments, I modified from another project that had more complex staging.

FROM node:20-alpine AS base
RUN npm i -g pnpm
COPY . /app

# all-dependencies required for both dev and build
FROM base AS all-dependencies
COPY ./package.json pnpm-lock.yaml /app/
WORKDIR /app
RUN pnpm i --frozen-lockfile

# production build, pnpm build builds the app, then the client, then the server.
# see scripts dir and server/package.json for details
# Will probably move to here later
FROM all-dependencies AS prod-build
WORKDIR /app
CMD ["pnpm", "build"]


# --target=prod
FROM base AS prod
COPY --from=prod-build /app/dist /app/dist
WORKDIR /app
CMD ["pnpm", "start"]

Now I can make this work by adding --force to the pnpm i command but it doesn't seem like that is the right solution.

What am I forcing and why am I having to?

Thanks

[isimmons]

I got past the pnpm update part by being explicit with npm i -g pnpm@latest so now it's back to the original problem.

[isimmons]

What I found so far is there is no "set" for setting "update-notifier" but both "updateNotifier" and "confirmModulesPurge" can be set via the --config flag when running the pnpm i command.

I found this through googling and AI help but nothing points to anything in the official docs and I can't find this using the search option in docs.

Is there a list of all available config options that can be set this way? The docs mention that pnpm uses the same config as npm but it looks like setting those configs is not all normalized.

In the npm docs I find update-notifier that can be set with "config set" but it can't be set that way in pnpm.

In the npm docs I don't find confirm-modules-purge and in pnpm it exists and can be set both ways.

FROM node:20-alpine AS base
RUN npm i -g pnpm@latest
# works
# RUN pnpm config set confirm-modules-purge false
# does not work
# RUN pnpm config set update-notifier false
# both of these work with used in the pnpm i command
ARG LEAVE_ME_ALONE_SHUT_UP_INSTALL_MY_DEPENDENCIES="--config.confirmModulesPurge=false --config.updateNotifier=false"
COPY . /app

FROM base AS all-dependencies
COPY ./package.json ./pnpm-lock.yaml /app/
WORKDIR /app
RUN pnpm i --frozen-lockfile ${LEAVE_ME_ALONE_SHUT_UP_INSTALL_MY_DEPENDENCIES}