chore: updated Dockerfile to change .meteor/ permissions to the node … #5353
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.
Resolves #5351
Resolves #5037
Impact: minor
Type: chore
Issue
When starting the reaction container on a fresh linux install I was met with permission issues within the container during startup. The issue was the owner of the
.meteor/local
was theroot
user and not thenode
user.Solution
Updated the dockerfile to create the
.meteor/local/
directory as well aschown
it to thenode
user. Also created a new volume within the docker-compose file for the local meteor directory.If you're solving a UIX related issue, please attach screen-caps or gifs showing how your solution differs from the issue.
Breaking changes
I think peoples using macOS may need to rebuild their container for this change to work.
Testing