Fix docker #142
Merged
Fix docker #142
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fixes issues with running the project on MacOS and utilizing Docker. The issue was with mounting volumes and running the backend, as well as restoring the database.
The backend was crashing when running bcrypt because the container architecture didn't support the execution of the bcrypt binary. This is fixed by simply ignoring node_modules in a .dockerignore file and forcing Docker to fetch packages compatible with the container's architecture.
The second issue is related to mongo restore and permissions. This has been fixed by adjusting the volumes and creating dedicated Dockerfiles for all layers of the app for simplicity and clarity.