# Node "prebuilt binary not found for musl" (Alpine) in CI

> Fix "prebuilt binary not found for ... musl" on Alpine in CI - a native package ships glibc prebuilds only, so musl-based Alpine cannot use them.

Source: https://latchkey.dev/learn/node-js/node-prebuilt-binary-musl-alpine-in-ci  
Updated: 2026-06-26

A native package publishes glibc prebuilds, but Alpine uses musl libc. With no musl prebuild and no compiler, the install fails on the libc mismatch.

## Diagnose it: reproduce the CI install locally

Install failures are usually environment drift rather than a broken lockfile: a different package-manager major, a different Node version, or a cache that is being restored from a run with different inputs. Reproduce the CI conditions before changing the lockfile, because regenerating it hides the real cause.

```Terminal
# match the runner exactly, then install from a clean slate
node --version && npm --version
rm -rf node_modules
npm ci --foreground-scripts

# if that succeeds locally but fails in CI, the difference is the cache
# or the package-manager version, not your lockfile
```

> Pin the package manager with Corepack (`"packageManager"` in package.json) so the runner and every developer machine resolve the same version. Version skew is the single most common source of lockfile errors that only appear in CI.

## Verify the fix survives a cold cache

A green run immediately after a fix often proves nothing, because it restored a cache written before the change. Force a cold install once to confirm the fix is real.

```.github/workflows/ci.yml
# temporarily bust the cache key to prove the fix on a cold runner
- uses: actions/setup-node@v4
  with:
    node-version: 22
    cache: npm
    cache-dependency-path: package-lock.json
# then bump this suffix once, run, and remove it
#   key: ${{ runner.os }}-node-${{ hashFiles('package-lock.json') }}-v2
```

## FAQ

### What causes Node "prebuilt binary not found for musl" (Alpine) in CI?

There are 2 common causes: package ships glibc-only prebuilds and alpine lacks the build toolchain to compile. The native package does not publish a musl variant, so Alpine has nothing compatible to download.

### How do I fix Node "prebuilt binary not found for musl" (Alpine) in CI?

There are 2 fixes depending on which cause you have: use a glibc base image and install musl build tools to compile from source. Work through them in order, since the first is the most common.

### What does Node "prebuilt binary not found for musl" (Alpine) in CI actually mean?

On an Alpine-based runner, a native dependency fails with "prebuilt binary not found" or a runtime "Error loading shared library ...

### How do I stop Node "prebuilt binary not found for musl" (Alpine) in CI happening again?

Prefer glibc base images for projects with native dependencies. The prevention section lists 3 changes that keep it from recurring.

---

Latchkey runs CI/CD that repairs its own failures. Agent entry points: https://latchkey.dev/agent.txt, https://latchkey.dev/openapi.json, https://latchkey.dev/llms.txt