Error: /app/node_modules/bcrypt/lib/binding/bcrypt_lib.node: invalid ELF header
A native module compiled for macOS/Windows is being loaded on Linux.
Exact message you may see
invalid ELF headerwrong ELF class
Seen on:
npm
Meaning
.node binaries are platform-specific. Copying node_modules into a Docker image or server from another OS causes it.
Common causes
- node_modules copied from the host into the container
- Shared volume between host and container
⚡ Quick fix
- Exclude node_modules via .dockerignore and run npm ci in the image
- Rebuild: npm rebuild
Detailed fix by platform
Docker
- bash
COPY package*.json ./ RUN npm ci COPY . .
How to diagnose
- Build — Where was node_modules created?
- Recent change — Did it start after a deploy, upgrade, or configuration change? Compare with the last working version.
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- 'sharp' is required to be installed in standalone mode Next.js: Error: 'sharp' is required to be installed in standalone mode for the image optimization to function correctly
- data directory permissions FATAL: data directory "/var/lib/postgresql/data" has invalid permissions — Permissions should be u=rwx (0700) or u=rwx,g=rx (0750).
- Docker Desktop requires privileged access (vmnetd) macOS: Docker Desktop needs privileged access / com.docker.vmnetd could not be started
Most viewed in npm
Other ways to find it
Where this error sits
Origin: Build & delivery. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Did this fix work for you?
Report a correction or suggest an improvement
Last updated 11 Oct 2026