Does pnpm start access the npm registry?

[omihirofumi]

When pushing a Docker image to Amazon ECR and deploying it to App Runner, I encounter the following error:
(It seems to fail at CMD ["pnpm", "start"].)

ERROR  GET https://registry.npmjs.org/pnpm: request to https://registry.npmjs.org/pnpm failed, reason: 

The script I am using is:
"start": "remix-serve ./build/bin/index.js"

When running the container locally with docker run, I do not get this error.

When executing the script directly, it works fine:
CMD ["node_modules/.bin/remix-serve", "./build/bin/index.js"]
So, I suspect that pnpm start is trying to fetch dependencies from the npm registry.

here is the Dockerfile

# syntax=docker/dockerfile:1

# Comments are provided throughout this file to help you get started.
# If you need more help, visit the Dockerfile reference guide at
# https://docs.docker.com/go/dockerfile-reference/

# Want to help us make this template better? Share your feedback here: https://forms.gle/ybq9Krt8jtBL3iCk7

ARG NODE_VERSION=20
ARG PNPM_VERSION=9.9.0

################################################################################
# Use node image for base image for all stages.
FROM node:${NODE_VERSION}-bookworm-slim AS base

WORKDIR /usr/src/app

# Update openssl 3.x
RUN apt-get update && apt-get upgrade openssl -y \
  && apt-get clean \
  && rm -rf /var/lib/apt/lists/*

# Install pnpm.
RUN --mount=type=cache,target=/root/.npm \
  npm install -g pnpm@"${PNPM_VERSION}"

################################################################################
# Create a stage for installing production dependecies.
FROM base AS deps

# Download dependencies as a separate step to take advantage of Docker's caching.
# Leverage a cache mount to /root/.local/share/pnpm/store to speed up subsequent builds.
# Leverage bind mounts to package.json and pnpm-lock.yaml to avoid having to copy them
# into this layer.
RUN --mount=type=bind,source=package.json,target=package.json \
  --mount=type=bind,source=pnpm-lock.yaml,target=pnpm-lock.yaml \
  --mount=type=cache,target=/root/.local/share/pnpm/store \
  pnpm install --prod --frozen-lockfile --ignore-scripts

################################################################################
# Create a stage for building the application.
FROM deps AS build

# Download additional development dependencies before building, as some projects require
# "devDependencies" to be installed to build. If you don't need this, remove this step.
RUN --mount=type=bind,source=package.json,target=package.json \
  --mount=type=bind,source=pnpm-lock.yaml,target=pnpm-lock.yaml \
  --mount=type=bind,source=.npmrc,target=.npmrc \
  --mount=type=bind,source=prisma,target=prisma \
  --mount=type=cache,target=/root/.local/share/pnpm/store \
  pnpm install --frozen-lockfile

# Copy the rest of the source files into the image.
COPY . .
# Run the build script.
RUN pnpm run build

################################################################################
# Create a new stage to run the application with minimal runtime dependencies
# where the necessary files are copied from the build stage.
FROM base AS final

# Use production node environment by default.
ENV NODE_ENV=production

# Run the application as a non-root user.
USER node

# Copy package.json so that package manager commands can be used.
COPY package.json .

# Copy the production dependencies from the deps stage and also
# the built application from the build stage into the image.
COPY --from=deps /usr/src/app/node_modules ./node_modules
COPY --from=build /usr/src/app/node_modules/.pnpm/@prisma+client*/node_modules/.prisma/client ./node_modules/@prisma/client
COPY --from=build /usr/src/app/build ./build

COPY --from=build /usr/src/app/prisma ./prisma

# Expose the port that the application listens on.
EXPOSE 3000

# Run the application.
CMD ["pnpm", "start"]
# CMD ["./node_modules/.bin/remix-serve", "./build/server/index.js"] # works file

[zkochan]

If there is a "packageManager" field in your "package.json" file then pnpm (or corepack) will download the version of pnpm specified there.

[omihirofumi]

Thank you for the response! That makes sense.
Indeed, my package.json contains "packageManager": "[email protected]".

However, why didn't I encounter this error when running docker run locally with the network turned off?
Also, I would like to know how to avoid this issue.

[omihirofumi]

@zkochan
Any updates on this?
Would appreciate any insights. Thanks!