-
Notifications
You must be signed in to change notification settings - Fork 0
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
Downloaded data are owned by root
#7
Comments
Might be fixed with the user ID fix from our docker compose recipes |
Blocked until https://neurobagel.github.io/dev-docs/sections/Docker/#running-docker-container-as-non-root-user is reviewed and we decide on how to solve issue |
Reviewed the docs, I think it still makes more sense to go with the user in the image. For one, that's what is recommended by OWASP and others (e.g. https://cheatsheetseries.owasp.org/cheatsheets/Docker_Security_Cheat_Sheet.html#rule-2-set-a-user). Secondly, it's easier to do than setting the |
Related to: |
The created
output/
folder is owned byroot
and cannot be modified without sudo, which might create issues for users.To get around this, we may want to consider updating our recommended
docker run
command (in the query tool?) to run as a non-root-user.The text was updated successfully, but these errors were encountered: