🐛(frontend) fix bind-mount hiding node_modules #206
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.
Narrow the bind-mount to ./src/frontend/apps/drive so that the node_modules folder created during the image build remains available inside the container. Solves: /bin/sh: next: not found when running make run-with-frontend.
Closes: #189
Purpose
Running the project with
make run-with-frontend
made the containerdrive-frontend-dev-1
exit immediately:$ next dev
/bin/sh: next: not found
The full
./src/frontend → /home/frontend/
bind-mount hid thenode_modules
directory produced during the Docker build stage, removingnode_modules/.bin/next
from the container’sPATH
.Proposal
Bind-mount only the sources that need hot reload (
apps/drive
) andstop masking the dependencies installed in the image.