-
Notifications
You must be signed in to change notification settings - Fork 5
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
uid in chroot context #6
Comments
I like the SUDO_UID option better. I can also provide an option to specify the uid just in case. |
vmalloc
added a commit
that referenced
this issue
Jul 27, 2012
Is the guid also handled in a similar fashion? |
Nope - I forgot to add the GID option - adding it now. |
vmalloc
added a commit
that referenced
this issue
Jul 28, 2012
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When running dwight through sudo, the uid in the chroot environment is 0 as well. It's desirable to have dwight command run in the same context of the calling user. I don't have a clean solution, here are some ideas:
The text was updated successfully, but these errors were encountered: