We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Love the container, thanks for it!
One of the challenges I'm facing is that the uid/gid that comes out for mounted volumes does is not controllable (unless I'm missing something).
Do you have any solutions or would gosu be a good solution here? I always hate to fork docker containers just to change uid/gid to my needs:
https://stackoverflow.com/questions/36781372/docker-using-gosu-vs-user
https://denibertovic.com/posts/handling-permissions-with-docker-volumes/
The text was updated successfully, but these errors were encountered:
Realize this is rather old issue, but the userns-remap is generally the way to go to handle this at the use level. See resources such as Isolate containers with a user namespace or Use Linux user namespaces to fix permissions in docker volumes
Sorry, something went wrong.
No branches or pull requests
Love the container, thanks for it!
One of the challenges I'm facing is that the uid/gid that comes out for mounted volumes does is not controllable (unless I'm missing something).
Do you have any solutions or would gosu be a good solution here? I always hate to fork docker containers just to change uid/gid to my needs:
https://stackoverflow.com/questions/36781372/docker-using-gosu-vs-user
https://denibertovic.com/posts/handling-permissions-with-docker-volumes/
The text was updated successfully, but these errors were encountered: