-
Notifications
You must be signed in to change notification settings - Fork 823
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
sudo doesn't work when "-u" flag is assigned #962
Comments
This should be resolved in the Insider build. Looks like it was closed out with some of our other fixes. Marking as fixed for insiders. |
Marked as fixed for some time. Closing it out. |
Which version is the bug fixed?
|
This is NOT fixed. On build 15063
This prevents some scripts from running, impeding dev work. |
Reopening because this is still broken. |
Having the same issue trying to access postgres.
|
any workaround to configure postgres till this gets fixed? |
It sounds stupid but try |
That doesn't seem to work
|
A workaround for me was to create the DB in the Windows environment, create the user and access it in Bash. It ultimately defeats the purpose of using Bash, so obviously, this isn't a solution but while it's bugged, this should work. |
Okay. Anyway, I've yet again wasted a couple of hours trying to get my RoR environment set up but looks like I still have to wait some more. Puma also fails with a weird `Read error: #<Errno::ENOPROTOOPT: Protocol not available - getsockopt(2)>` error. Bash for Windows is still not currently there yet for any dev work.
On 18-Apr-17 11:34:42 PM, Daniel Ingolfsson <notifications@github.com> wrote:
A workaround for me was to create the DB in the Windows environment, create the user and access it in Bash.
It ultimately defeats the purpose of using Bash, so obviously, this isn't a solution but while it's bugged, this should work.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub [#962 (comment)], or mute the thread [https://github.com/notifications/unsubscribe-auth/AB5qVwU0VFKeeBA3SskAEmJhi-YRZR6eks5rxQJCgaJpZM4JpdEs].
|
@ArsalanDotMe -- in your previous comment, you want That said, it's definitely true that getting system services like PostgreSQL working within WSL is still a pain. Fortunately, it sounds like it's being worked on. |
@aseering - you're correct I've filed a bug and will be looking into this. |
@ArsalanDotMe - Thanks for your post and patience with WSL. WSL is still a beta feature and while we have covered some ground in Creators Update, there is still more to go. And, your input here actually helps us getting there meaningfully. So, I wouldn't consider your two hours a complete waste :). Would you be willing to open a new issue for the We are trying to get "full" compatibility with Linux and as you can imagine, that's a huge surface area. Hopefully, that explains some of the time that we are taking here to cover the ground. |
A workaround that I used is |
Just ran into this myself. Thanks for the workarounds! Both That said, I am now hitting issues as seen in #61 |
Thanks to everyone for the help. I got some time to take a look at this and the issue was our driver not correctly setting the "saved-set" UID or GID on set-user-ID and set-group-ID bit binaries. I have a fix for this and it will be available in a Windows Insider build soon. |
This is fixed in 16251. |
sudo command doesn't when '-u' flag is assigned.
For example,
sudo -u user ls
The command should be run
sudo: setresuid() [1000, 1000, 1000] -> [-1, 0, -1]: Operation not permitted
windows 10 1607 x64
Steps / commands required to reproduce the error
sudo -u user ls
Strace of the failing command
None
See our contributing instructions for assistance.
The text was updated successfully, but these errors were encountered: