-
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
unshare failed: Invalid argument #2981
Comments
You are correct, we have not yet implemented user namespaces. |
@therealkenc well, I replaced the chroot with Void linux(because I want to write xbps package templates and the xbps-src script needs xbps-uunshare(which requires the
here is where it crashes(I suspect) EDIT: fixed broken links |
hope user namespaces sooner got implimented . |
@therealkenc, are you still working on it? |
Wasn't the person "working on it". I take boypt at face value above, which would imply it was not implemented in WSL1. There is also #3282 which I suspect (but can't prove) is a side effect of chrome no longer supporting SUID sandbox (nor
|
@therealkenc, strange, I used WSL2. My issue is similar to @tim241's. |
Tim241 didn't have a repro so that post was glossed in January; this was before WSL2, and thus not too surprising a fail at the time. But as it happens I'm working on something in a space (almost) related Void Linux at the moment, so you've made me look on the lark. I was able to reproduce Tim's scenario on WSL2. There is an easier repro than the With the entirely predictable strace:
Which is nutty (at least in my somewhat sleep deprived state) because outside the chroot (back in plain 'ole Ubuntu): Which I already knew worked because I had done it before. At a loss right this moment to guess the variable. On first glance it is hard to finger-point WSL, because user namespaces is enabled in the kernel and, well, your know, works. But it is also near-impossible to finger-point Void userspace, because I can't think of anything that Void userspace could do to make the Reason will probably be obvious once it comes to me; if someone else doesn't beat me to it. Appreciate the submission. |
@therealkenc it seems like intended behavior :) |
There is an article of void-packages repo, which suggests to modify chroot's permissions. |
I was afraid of that. Thanks. [edit] Someone gets a gold star if they can concisely describe why |
This would be useful to automate #5090 (comment) as per https://stackoverflow.com/questions/20553039/forcing-usermod-with-running-program/56338192#comment109450754_56338192 |
Microsoft Windows [Version 10.0.17107.1000]
I'm trying to get
unshare -U
to work but whenever I try to execute that command I get:it seems like WSL doesn't have User Namespaces implemented(CONFIG_USER_NS)
unshare.strace
The text was updated successfully, but these errors were encountered: