-
Notifications
You must be signed in to change notification settings - Fork 519
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Application Crashing When Using bcrypt's compare function on node docker image #1047
Comments
same problem here node:20-alpine, any workaround please? |
use 5.1.0 |
what I did to fix this problem was:
volumes: instead of just: volumes: and ran docker-compose build before docker-compose up |
same problem with |
look at my answer above your comment and see if anything I changed in my compose file helps you. |
I understand the problem, there is some library mismatch on alpine images. One solutions is using hosts node_modules, but that its is not viable solution when you dont build the project on host but inside of another container running alpine, speaking of some CI/CD stuff etc. In my case i used version 5.10, which is fine. |
I had the same issue, installing version 5.1.0 fixed it. |
if anyone still having this issue, using docker image |
Title:
Application Crash with bcrypt's compare function on node docker image
Description:
I ran into an issue where my application crashes when using the compare function from bcrypt on the node Docker image.
Here are the details:
Steps to Reproduce:
Use the node Docker image in a Node.js application.
Utilize bcrypt's compare function to compare hashed passwords.
Observe the application crash upon invoking the compare function.
Expected Behavior:
The application should successfully execute the compare function without crashing.
Actual Behavior:
The application crashes when calling the compare function without throwing any specific error.
Additional Details:
Dockerfile:
and this is my docker-compose.yml:
I read on this issue it could be a library mismatch, but I tried using a .dockerignore file and nothing changed.
Any suggestion on what I could do?
The text was updated successfully, but these errors were encountered: