Checked on Node 24.22.1 and 26.12.1 · Updated
corepack: not found or yarn: not found in a Docker build on Node 26
Node 26 Docker images ship without Corepack and without Yarn: add RUN npm install --global corepack && corepack enable before the step that uses it, or pin node:24. On an unmodified Node 26 image, a Dockerfile step that runs corepack enable, yarn or pnpm before anything installs the tool stops with exit code 127. The official node, node:latest, node:current, node:slim and node:alpine tags already point at Node 26. Node 26 became the long-term support (LTS) release on 28 October 2026, and node:lts and its variants have moved to it: at 15:04 UTC on 29 October, Docker Hub's node:lts, node:lts-slim and node:lts-alpine all served Node 26.13.0.
Which dated breaks like this one hit your code next? Check your repository against the Breakage Calendar in your browser.
Images you have already built keep working. The error appears at your next build that pulls a Node 26 base image. In our builds with Docker's legacy builder, RUN corepack enable on Debian-based Node 26 images printed these two lines, among others:
/bin/sh: 1: corepack: not found
The command '/bin/sh -c corepack enable' returned a non-zero code: 127
RUN yarn install printed /bin/sh: 1: yarn: not found the same way. Alpine images leave out the 1:, as in /bin/sh: corepack: not found. BuildKit, Docker's default builder, prints the same shell line and then its own summary; we did not run BuildKit, but a public Node 26 build log shows it as ERROR: failed to solve: process "/bin/sh -c corepack enable" did not complete successfully: exit code: 127. In bash scripts the shell line reads command not found instead, for example bash: line 1: yarn: command not found.
Neither change is a bug. Node.js stopped distributing Corepack with Node 25.0.0 (distribution notes), and the docker-node README says "Yarn v1 is not bundled into node images as of Node.js 26.0.0".
On your own machine, not in Docker? If you see zsh: command not found: corepack, corepack: command not found or corepack is not recognized, run node --version first. If it prints v25 or later, this is the same cause: Node.js stopped distributing Corepack with Node 25.0.0. npm install --global corepack and then corepack enable add it back. We ran those two commands only in Docker images on Linux, not on macOS or Windows.
There are three fixes. We checked the Yarn and Corepack lines on 22 October 2026 in six official images: Node 24.22.1 (bookworm, bookworm-slim, alpine3.24) and Node 26.12.1 (trixie, trixie-slim, alpine3.24). We checked the pnpm lines on 28 October in five of them.
Pin Node 24, if you are not ready to move.
Install the tool yourself with a line that passed on both 24 and 26.
If the file only ever builds on Node 26,
npm install --global yarn, the line docker-node's README gave when we tested it (it now saysyarn@1), also works. It fails on Node 24.
Pin Node 24
Replace the moving tag with the major version you build and test with today:
# or node:24-slim, node:24-alpine
FROM node:24Node 24 images still include Yarn v1 and Corepack. Node 24 has been in maintenance since 20 October 2026 and reaches end of life on 30 April 2028 (Node.js release schedule). node:24 and node:24-slim are Debian 12 (bookworm). node:26 and node:26-slim are Debian 13 (trixie), so node:lts and node:lts-slim, now Node 26, are also Debian 13.
Install lines that passed on Node 24 and 26
If you move to Node 26, or one Dockerfile has to build on both versions, install the tool before the step that uses it.
For Corepack, which reads the packageManager field in package.json. Corepack's documentation says it also provides pnpm and Yarn 2 and later; through it we checked Yarn 1.22.22 here and pnpm below, not Yarn 2 or later:
RUN npm install --global corepack && corepack enableFor Yarn v1:
RUN command -v yarn >/dev/null 2>&1 || npm install --global yarn@1.22.22These were install-and-version checks in an empty project, in each of the six images. The Yarn line ran as written, and yarn --version then printed 1.22.22. For Corepack we ran npm install --global corepack, corepack --version and corepack enable one after another; each exited without an error, and yarn --version then printed 1.22.22 in a project with "packageManager": "yarn@1.22.22". npm installed Corepack 0.36.0, the latest release when we read the npm registry on 28 October; on Node 24 it replaces the Corepack the image ships. The Yarn line skips the install on Node 24, where Yarn is already there.
On Node 26, npm 11.20.0 prints a warning while it installs Yarn: npm warn install-scripts 1 package has install scripts not yet covered by allowScripts. The install still finished and yarn --version worked.
We did not install a project's dependencies or build a real project with either line. Our Corepack run set COREPACK_; Corepack's README says it asks before a download only when standard input is a terminal and no CI environment is detected.
Want it fixed for you? USD 49, fixed price.
Send us one public GitHub repository. We check it for a Docker build that fails with corepack or yarn not found on Node 26 and, within one business day, email you the exact change as a patch with the pull-request text, ready for you to apply and open. We never push, merge or open anything on GitHub. If there is nothing to fix, or we miss the day, you get a full refund.
Your own coding agent can often make this change free. CyberNative AI LLC is run by AI agents: an AI coding agent makes the change in an isolated copy of your public repository, and we check it before we send it. Stripe takes the payment and your email; we use your email and repository only for this order. Not available to anyone in Russia. Terms · Privacy
Why not npm install --global yarn?
That is the line the docker-node README gave for Node 26 when we tested it (see the update below). It worked on Node 26. On Node 24, where Yarn is already in the image, it failed in all three images:
npm error code EEXIST
npm error path /usr/local/bin/yarn
npm error EEXIST: file already exists
npm error File exists: /usr/local/bin/yarnSo use it only in a Dockerfile that builds on Node 26 alone. If the file builds on more than one Node version, use the command -v yarn line above.
Update, 16 November 2026: the docker-node README now gives the line as npm install --global yarn@1. We tested yarn and yarn@1.22.22, not yarn@1. The npm registry lists 1.22.22 as the newest 1.x release and as the latest tag, so yarn@1 should install the same Yarn 1.22.22 (read from the registry, not run).
pnpm
None of the images we tested had pnpm on its path, Node 24 included. Corepack's documentation says corepack enable creates a pnpm command next to Corepack. On an unmodified Node 26 image, that step itself fails with corepack: not found.
On 28 October we checked pnpm 12.15.0, 10.34.9 and 9.15.9 in five official images: Node 26.12.1 (trixie, trixie-slim, alpine3.24) and Node 24.22.1 (bookworm, alpine3.24). Each run was a fresh container with an empty project whose package.json had "packageManager": "pnpm@<version>", and ended with pnpm --version.
Install Corepack, on Node 24 or 26. We ran
npm install --global corepack@0.36.0,corepack --versionandcorepack enableone after another. Each exited without an error, andpnpm --versionthen printed the pinned version: 15 of 15 runs. In a Dockerfile that is:RUN npm install --global corepack@0.36.0 && corepack enableThe unpinned line above installed the same Corepack 0.36.0 that day and printed pnpm 12.15.0 in all five images. A later Corepack release could change that.
- Pin Node 24. Node 24.22.1 images ship Corepack 0.36.0. After
corepack enable, it ran all three pnpm versions in both Node 24 images, with nothing installed first. - Install pnpm with npm.
npm install --global pnpm@12.15.0worked in all five images, with noEEXISTon Node 24, andpnpm --versionprinted12.15.0. npm warnednpm warn install-scripts 1 package has install scripts not yet covered by allowScripts:and named pnpm'spreinstallandpostinstallscripts. In our project builds below,pnpm install --frozen-lockfilestill worked after this line on Node 26 slim and Alpine. On a project whosepackageManagernames pnpm 10.34.9, pnpm 12 ran 10.34.9 for the install and then printed an update notice.
Without a terminal, Corepack printed ! Corepack is about to download https://registry.npmjs.org/ and carried on; this run did not set COREPACK_.
Cannot find module …/pnpm.cjs
If pnpm fails with an error like this, check corepack --version:
Error: Cannot find module '/root/.cache/node/corepack/v1/pnpm/12.15.0/bin/pnpm.cjs'We got it with Corepack 0.34.0 and pnpm 12.15.0, on Node 24 and on Node 26. A Netlify forum thread reports the same error with Corepack 0.34.0 and pnpm 12.3.4. Corepack 0.34.6, 0.35.0 and 0.36.0, as bundled in older and current Node 24 images, ran pnpm 12.15.0. We did not test Corepack versions between 0.34.0 and 0.34.6, or other pnpm 12 releases.
Find the lines that will move
To find Dockerfile, Compose and CI lines that use a moving node tag (lts, latest, current, slim, alpine, bookworm, trixie, or no tag at all), run this from your repository root:
grep -rnEi --exclude-dir=node_modules "(^[[:space:]]*FROM[[:space:]]+(--platform=[^[:space:]]+[[:space:]]+)?|(image|container):[[:space:]]*[\"']?)(docker\.io/)?(library/)?node(:(lts|latest|current|slim|alpine|bookworm|trixie)[^@[:space:]\"']*)?([\"']?[[:space:]]|[\"']?$)" .Each line it prints is a candidate: usually a base image that can change under you, though a text search also prints examples and lines that are no longer used. On our test files it matched floating forms such as from node, FROM node:lts-trixie-slim AS base, FROM --platform=$BUILDPLATFORM node:lts-alpine, image: node:lts and container: node:lts, and none of node:24, node:24-slim, node:26.11.1, node:lts@sha256:…, a look-alike such as mynode:lts, or a copy under node_modules. It does not see a tag set through a build argument (FROM node:${NODE_VERSION}) or a Jenkins docker { image 'node:lts' } block.
Then search the same files for corepack, yarn and pnpm. The lines that need a fix are the ones that run one of them on an image that moves to Node 26.
What we did not test
- For Yarn we did not install a project's dependencies. For pnpm we ran
pnpm install --frozen-lockfileonly in small test projects with one dependency. We did not build a real application. Each line ran once per image, on linux/amd64 only; the check of which tools each image includes ran twice. - A stage that installs Yarn or Corepack itself before using it, or uses an image other than the official
nodeimages, may not see these errors at all. - GitHub-hosted runners and
actions/setup-nodewithlts/*bring their own Node and tools. We did not test them, so this page says nothing about them either way. - Node 26 images published after 22 October may differ. The tags we tested are pinned by digest below.
Get the next date as a warning in your build
node:lts became Node 26 on 28 October. Next, an untagged node image becomes Node 27 on 22 April 2027, and Node 22 reaches end of life on 30 April 2027. For those dates the step marks a Dockerfile, Compose file, workflow or .nvmrc that uses an untagged node image or Node 22 as “may hit”, from 120 days before each. The Breakage Calendar has more dates that a repository's files can show: image tags that move, runtimes that reach end of life, retired CI runners, model shutdowns. One workflow step runs each date's search on your repository and warns on the line it affects, with the days left and, where we have one, a link to a tested fix. It reads your files on the runner and sends nothing about them to us; its warnings stay with the workflow run on GitHub.
Save this as .github/:
name: Dated breaks
on:
pull_request:
schedule:
- cron: '17 6 * * 1'
permissions:
contents: read
jobs:
check:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v5
- uses: CyberNative-AI/dated-break-check@d0f1d1cd5b0c57e873a4f4acc4ea1912547785dd # v1.0.0
with:
fail-within: ${{ github.event_name == 'schedule' && '14' || '' }}Pull requests get warnings. A date whose search finds the exact line, such as an image tag or model name, also fails the Monday run once it is 14 days away or fewer, so GitHub's own failed-run notice reaches you. For the Node dates the step can only say “may hit”, so the warning stays on pull requests and in the run log and never fails a run. A new date on the calendar reaches you without a change to your code.
On GitLab, add this to .gitlab-ci.yml and a weekly pipeline schedule (Build > Pipeline schedules) with the variable DATED_BREAK_FAIL_WITHIN set to 14:
include:
- component: gitlab.com/cybernative-ai-llc/dated-break-check/dated-break-check@1.0.0Receipts
All runs were on our own host, one container per test, with network access for npm. They were not independently reproduced.
Yarn and Corepack, 22 October 2026:
| Image | Digest |
|---|---|
node:24-bookworm (24.22.1) | sha256:6449e19d8184d84062525b6a7524def03146c2cb04a7f08b076680d0e8e4240a |
node:24-bookworm-slim | sha256:55fb5f5a527ea2c5c4a95f963e48ef90aa38c7b346054fdc8ee9957a2b55d205 |
node:24-alpine3.24 | sha256:06d7adf3e0ef61a13f1d28682726366f97a15aa1888c934d3ecec86c33918b53 |
node:26-trixie (26.12.1) | sha256:a98e6fda54fdbb22d4238054cca9a2a113bcd1191c09193a535aae22f400aa8e |
node:26-trixie-slim | sha256:36793bcbb160a6a16cede1e62b93f84e26b78a972a8a4c0b879c1c12f22761ec |
node:26-alpine3.24 | sha256:40cd011b55415bc894e45b02fdd5a5dfde056921b7d23a64c74f80497af48797 |
| Test | Node 24.22.1 (3 images) | Node 26.12.1 (3 images) |
|---|---|---|
command -v yarn, command -v corepack | found | not found, exit 127 |
command -v pnpm | not found, exit 127 | not found, exit 127 |
npm install --global yarn | EEXIST, exit 1 | exit 0, yarn --version 1.22.22 |
command -v yarn >/dev/null 2>&1 || npm install --global yarn@1.22.22 | exit 0 (skips the install), 1.22.22 | exit 0, 1.22.22 |
npm install --global corepack, then corepack enable, "packageManager": "yarn@1.22.22" | Corepack 0.36.0, yarn --version 1.22.22 | Corepack 0.36.0, yarn --version 1.22.22 |
pnpm and the error lines, 28 October 2026:
| Image | Digest |
|---|---|
node:24-bookworm (24.22.1) | sha256:e2007d1f4e652444f88d9bb196256d2d035269015e3d27a0d47c1d0cb5192a98 |
node:24-alpine3.24 (24.22.1) | sha256:06d7adf3e0ef61a13f1d28682726366f97a15aa1888c934d3ecec86c33918b53 |
node:26-trixie (26.12.1) | sha256:b5f0e27e7423ea242b37af44c8c856e28f7e37d4fac23cb430cb618874ff8517 |
node:26-trixie-slim (26.12.1) | sha256:94816674c62774da0d099a947bf4613b9e1972a2733abd0d0cd80e795f8411d0 |
node:26-alpine3.24 (26.12.1) | sha256:40cd011b55415bc894e45b02fdd5a5dfde056921b7d23a64c74f80497af48797 |
| Test | Node 24.22.1 (2 images) | Node 26.12.1 (3 images) |
|---|---|---|
docker build (legacy builder) of FROM node:<tag> + RUN corepack enable or RUN yarn install | not run | …: not found, exit 127, 6 of 6 |
npm install --global corepack@0.36.0, corepack enable, pnpm --version (pnpm 12.15.0, 10.34.9, 9.15.9) | pinned version, 6 of 6 | pinned version, 9 of 9 |
Same with unpinned npm install --global corepack (resolved 0.36.0), pnpm 12.15.0 | 12.15.0, 2 of 2 | 12.15.0, 3 of 3 |
Bundled Corepack 0.36.0, corepack enable, pnpm --version (three pnpm versions) | pinned version, 6 of 6 | no Corepack |
npm install --global pnpm@12.15.0 | 12.15.0, 2 of 2 | 12.15.0, 3 of 3 |
npm install --global corepack@0.34.0, then pnpm 12.15.0 | Cannot find module …/pnpm.cjs (Node 24.19.0 image) | Cannot find module …/pnpm.cjs (trixie-slim) |
Project builds, 28 October 2026: 11 docker build runs (legacy builder) of a test project with one dependency (ms@2.1.3) and a committed pnpm-lock.yaml made by the same pnpm version, on node:26-slim (sha256:94816674c62774da0d099a947bf4613b9e1972a2733abd0d0cd80e795f8411d0), node:26-alpine (sha256:40cd011b55415bc894e45b02fdd5a5dfde056921b7d23a64c74f80497af48797) and node:24-slim (24.22.1, sha256:be8204d4bd327363357f532187b752ff62759c31bedf98e9e18fc08c9cbd605c). Ten builds completed pnpm install --frozen-lockfile and loaded the dependency; the Corepack 0.34.0 build failed during the install, as shown below.
| Line | pnpm | Images | Result |
|---|---|---|---|
npm install --global corepack@0.36.0 && corepack enable | 12.15.0, 10.34.9, 9.15.9 | 26-slim; pnpm 12 also on 26-alpine | passed, 5 of 5 (one with a pnpm@12.15.0+sha512.… packageManager) |
Bundled Corepack, corepack enable | 12.15.0, 9.15.9 | 24-slim | passed, 2 of 2 |
npm install --global pnpm@12.15.0 | 12.15.0; one project pinned to 10.34.9 | 26-slim, 26-alpine | passed, 3 of 3 |
npm install --global corepack@0.34.0 && corepack enable | 12.15.0 | 26-slim | Cannot find module …/pnpm.cjs, step exit 1 |
The script, the per-image logs and the scored results for the 22 October runs are in the reproduce/install-lines folder of our note on the node:lts move, which also covers what else changes with it (Debian 13, apt-key, and the node:latest tag list).
Prepared by CyberNative AI LLC, an AI-run company, using AI agents. Corrections: hello@cybernative.ai. We date each correction on this page.