Expected directory: node-v83-linux-x64-musl. Found: [node-v72-linux-x64-musl]
See original GitHub issueGrpc 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:
- Created 3 years ago
- Reactions:5
- Comments:8 (4 by maintainers)
Top 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 >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
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 runningnpm rebuild
in the Dockerfile (may also need the--unsafe-perm
argument), or by runningnpm install --target=12.0.0 --target_platform=linux --target_arch=x64 --target_libc=musl
outside of the docker image.Hi @murgatroid99, is there a place where I can check the currently supported node version?