bcrypt invalid elf header when running node app

I've found that bcrypt compiled on OSX will not quite work on Linux. In other words, if you check in the bcrypt compiled on your local OSX workstation, and try to run the node app on your linux servers, you will see the error above.

Solution: npm install bcrypt on Linux, check that in, solved.

Probably the best way to deal with this is exclude your node_modules in .gitignore... and npm install remotely.

If you are running inside a docker container as I am, all you need is a .dockerignore with 'node_modules' specified in it.

Some libraries need to be compiled on the host machine and therefore your modules can be stale.

My issue was with my docker-compose.yml file, I already had node_modules in my .dockerignore but I also needed to add the node_modules directory as a volume:

volumes:
  - ./:/usr/src/app
  - /usr/src/app/node_modules

There is a simple way that allowed me to solve this problem:

1. Uninstall bcrypt

npm uninstall bcrypt

2.- Install bcrypt again

 npm i bcrypt

The error occurs because when you install bcypt, npm installs the recommended version for your machine and operating system, but when you are on another machine, this doesn't work.

-------- UPDATE ----------------------------------------

It also seems to me that another solution which is to grant root permissions to bcrypt installation, it happens because bcryp uses its own user but it has no permissions, so:

1. You must grant root permission to your project folder. go outside of your project folder and then

sudo su

Then enter your root password to get root user permissions

2. Grant permission to your project folder

chmod -R 777 <project_folder>

3. Go to your project folder and install bcrypt

cd <project_folder>

AND

npm i bcrypt --unsafe-perm=true --allow-root --save

Ready, if everything was OK, your bcrypt module will install without problems.

I came across the same problem. I deployed by code in AWS Lambda using windows. I got the same error. I fixed it using 'bcryptjs' npm library.

npm install bcryptjs

change package to:

npm install bcryptjs

var bcrypt = require('bcryptjs');

The functions are the same.

Get more information here https://github.com/dcodeIO/bcrypt.js

I was also facing the same issue with bcrypt v.1.0.3. Just updated to the latest version (3.0.1) and its working fine now

Run

npm install bcrypt@latest --save

To solve this problem for a Docker container.

You can create a .dockerignore with this configuration :

node_modules/
dist/

in my case I was using nodejs in windows, when I use docker (with linux) I got that error, add the .dockerignore file with the folder node_modules and with this I work correctly, the nodejs packages in windows load differently in linux, so it is better that you install them from scratch in linux.

If you are in Docker I resolve the issue by logging in to the maching running my service and running npm uninstall bcrypt and then npm install bcrypt

First make sure you are not uploading the node modules and are running npm install on your linux machine itself as bcrypt installation can vary depending on the platform you use. You can look at other installation instructions for other platforms below.
https://github.com/kelektiv/node.bcrypt.js/wiki/Installation-Instructions

If you are having further problems it could be related to node-pre-gyp. A dependency of bcrypt.

For AWS Elastic Beanstalk When deploying to Elastic Beanstalk running Node 8.x, node-gyp doesn't have sufficient permissions to write to the tmp directory. bcrypt won't install and the application deployment will fail.

A workaround is to add a .npmrc file to the root of your project that will force node-gyp to run as root and allow the installation to complete. File contents for .npmrc:

# Force npm to run node-gyp also as root, preventing permission denied errors in AWS with npm@5 or @6
unsafe-perm=true

Another alternative (Perhaps the more right way) is to make .ebextensions file with code:

.ebextensions:00_change_npm_permissions.config:
  "/opt/elasticbeanstalk/hooks/appdeploy/post/00_set_tmp_permissions.sh":
    mode: "000755"
    owner: root
    group: root
    content: |
      #!/usr/bin/env bash
      chown -R nodejs:nodejs /tmp/.npm

This will give you sufficient access to run node-gyp

For those deploying an app to AWS elastic beanstalk, and gonna install bcrypt on the server, include in a post deploy hook in .ebextensions/01_build.config:

files:
  "/opt/elasticbeanstalk/hooks/appdeploy/post/99_build_app.sh":
    mode: "000755"
    owner: root
    group: root
    content: |
      #!/usr/bin/env bash
      cd /var/app/current/
      rm -rf node_modules/bcrypt
      sudo /opt/elasticbeanstalk/node-install/node-v10.13.0-linux-x64/bin/npm install bcrypt@latest

may be a difference in architecture, using the google compute engine i run this on my google cli putty or google terminal:

npm uninstall bcrypt

then

npm i bcrypt

this should fix it

I know that this might be a bit of a hassle but it is a solution. What I did when I needed to implement Bcrypt, was I started a Cloud 9 instance. For those of you who don't know, Cloud9 is a basic AWS IDE that runs on an EC2 instance. From Cloud9 you are able to upload your code on the ide as a lambda function. So I wrote the function on Cloud9 and when I uploaded it, the code worked.

I usually use macOS with Docker, to add some packages I first go into the Docker server docker exec -it nameServer /bin/bash and then add the package npm install bcrypt for example. So I guarantee everything will go run on the production server