Need help?

Our experts have had an average response time of 11.7 minutes in August 2021 to fix urgent issues.

We will keep your servers stable, secure, and fast at all times for one fixed price.

Install Bcrypt in Docker and resolve common errors

by | Apr 16, 2021

Wondering how to install Bcrypt in Docker? We can help you.

Most of our customers use Bcrypt npm package to work with passwords in JavaScript.

As part of our Docker Hosting Support, we assist our customers with several Docker queries.

Today, let us see how to install Bcrypt in docker and how to resolve the related errors.


Install Bcrypt in Docker

The Bcrypt package to encrypt passwords comes with a minor challenge. While we install, it needs to comply with the operating system (OS) architecture using node-gyp, python 2.x.

On occurrences of any code change to the application, the docker image will need a rebuild to check those changes. This will add time for every change to check, creating a slow feedback loop.

In order to solve this, we can use docker named volumes, which will link application files on our host to the docker container.


Setup Dockerfile to build Bcrypt

Initially, we run the below command on our Dockerfile:

RUN apk add –no-cache make gcc g++ python && \
npm install && \
npm rebuild bcrypt –build-from-source && \
apk del make gcc g++ python

This will install all the prerequisites for Bcrypt, then install node_modules, and then compile Bcrypt.

Afterward, it will remove the prerequisites to keep the docker image small as possible.

The challenge is during the development, while we work on a different OS to the Docker Container.

For instance, consider we work on Windows. However, the docker image built is Linux.

This will cause an error when running the app because Bcrypt dependency complies against the host (Windows).

Error: /app/node_modules/bcrypt/lib/binding/bcrypt_lib.node: invalid ELF header


How to solve this?

In order to solve this, we need to set up a docker-compose.yml file with a volumes field that can create a named volume to link our host files to the container.

When the host has a different OS, Bcrypt node_module will cause the error. So, we need a way to exclude the node_modules on the host machine from being linked to the container.

For that, we need to use an anonymous volume.

An example snippet of the docker-compose file is given below:

– ./your-host-app:/usr/src/app # named volume
– /usr/src/app/node_modules # anonymous volume for node_modules only

Anonymous volumes reference the directory in the container. On the other hand, docker handles where to store the files.

The mount is outside of our project. This keeps the node_modules intact.

While docker-compose up, will create anonymous volume for new containers, docker-compose down does not remove them.

However, the flag -v can remove them. If we only want to remove anonymous volumes, we can stop the containers and run docker-compose rm -vf.

[Need help with the procedures? We can help you]



In short, we saw how our Support Techs install Bcrypt in Docker and how they solve relating errors.


Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.


var google_conversion_label = "owonCMyG5nEQ0aD71QM";


Submit a Comment

Your email address will not be published. Required fields are marked *



Privacy Preference Center


Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]


Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid


Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie


These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.