You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Given that we mount host directories to the container in several of our tools/services (e.g., graph, CLI) and create files on the host as a result, we should provide a workaround to write these files not as root (default), so that users can easily modify or delete them on the host afterwards if needed without permission issues.
We want to keep our issues up to date and active. This issue hasn't seen any activity in the last 75 days.
We have applied the _flag:stale label to indicate that this issue should be reviewed again.
When you review, please reread the spec and then apply one of these three options:
prioritize: apply the flag:schedule label to suggest moving this issue into the backlog now
close: if the issue is no longer relevant, explain why (give others a chance to reply) and then close.
archive: sometimes an issue has important information or ideas but we won't work on it soon. In this case
apply the someday label to show that this won't be prioritized. The stalebot will ignore issues with this
label in the future. Use sparingly!
Given that we mount host directories to the container in several of our tools/services (e.g., graph, CLI) and create files on the host as a result, we should provide a workaround to write these files not as root (default), so that users can easily modify or delete them on the host afterwards if needed without permission issues.
As a starting point, see: https://hackmd.io/@neurobagel/HyGSQ-Ip6#Running-Docker-container-as-non-root-user
The text was updated successfully, but these errors were encountered: