question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Expected directory: node-v83-linux-x64-musl. Found: [node-v72-linux-x64-musl]

See original GitHub issue

Grpc version: 1.24.2

When deploying my Node.js app I have a problem with the binary file for grpc package.

Error:

Error: Failed to load gRPC binary module because it was not installed for the current system
Expected directory: node-v83-linux-x64-musl
Found: [node-v72-linux-x64-musl]
This problem can often be fixed by running "npm rebuild" on the current system
Original error: Cannot find module '/app/node_modules/grpc/src/node/extension_binary/node-v83-linux-x64-musl/grpc_node.node'

I tried these commands in the Dockerfile:

  • npm rebuild
  • npm install --unsafe-perm
  • npm install --target=13.0.0 --target_platform=linux --target_arch=x64

Dockerfile (found here):

FROM node:lts-alpine
WORKDIR /app

COPY package*.json ./

RUN apk add --no-cache --virtual .gyp \
        python \
        make \
        g++ \
    && npm install \
    && apk del .gyp gcc g++ python

COPY . .

RUN npm run build

EXPOSE 9080

CMD ["npm", "start"]

Also I tried to configure binaries’ location, but didn’t found node-v83-linux-x64-musl. Configure binaries location

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Reactions:5
  • Comments:8 (4 by maintainers)

github_iconTop GitHub Comments

21reactions
murgatroid99commented, Jun 4, 2020

Module version 83 corresponds to Node 14, not 13. Unfortunately, we have not yet published binaries for Node 14, so it’s going to be difficult to get that working. You should still be fine with Node 12. If you switch to node:12-alpine, you can install the proper binary file either by running npm rebuild in the Dockerfile (may also need the --unsafe-perm argument), or by running npm install --target=12.0.0 --target_platform=linux --target_arch=x64 --target_libc=musl outside of the docker image.

2reactions
laike9mcommented, Jul 2, 2020

Hi @murgatroid99, is there a place where I can check the currently supported node version?

Read more comments on GitHub >

github_iconTop Results From Across the Web

Expected directory: node-v83-linux-x64-musl. Found
I tried these commands in the Dockerfile: npm rebuild; npm install --unsafe-perm; npm install --target=13.0.0 --target_platform=linux -- ...
Read more >
node-linux-x64 - npm
Start using node-linux-x64 in your project by running `npm i node-linux-x64`. There are no other projects in the npm registry using ...
Read more >
Hyperledger Fabric: Error: Failed to load gRPC binary module ...
Expected directory : node-v64-linux-x64-glibc. Found: [node-v57-linux-x64-glibc] This problem can often be fixed by running “npm rebuild” on ...
Read more >
Node v14.15.4 (LTS)
Affected Node.js versions are vulnerable to a use-after-free bug in its ... https://nodejs.org/dist/v14.15.4/node-v14.15.4-linux-x64.tar.xz
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found