-
Notifications
You must be signed in to change notification settings - Fork 150
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
write sysctl key kernel.domainname: open /proc/sys/kernel/domainname: permission denied: unknown #287
Comments
Hi @mfriedenhagen, that's right, I would expect this problem to be only reproduced when operating in |
@mfriedenhagen just to let you know that I have fixed this one as part of various enhancements that I've been making to sysbox-fs. I expect to have all those merged within the next few days, so you should have a fix for this one soon. |
Fixed for this one was merged a while ago as part of Sysbox v0.4.0 release. Please let us know if have any other question on this matter. |
My understanding is that this issue was resolved by sysbox when running the system container with I just wonder if I should create a separate issue to track it. |
Hi @felipecrs! In regards to the first issue, Sysbox is working as expected here by preventing the user from writing to this procfs' system-wide resource ( Btw, there's already a few other sysbox-fs handlers doing something very similar -- Will look at the other issue you raised ( |
Sounds awesome! I'll try and let you know how it works. Thanks a lot.
|
👍 |
@rodnymolina please disregard my concern about |
I am unable to set the
domainname
. Actually I use docker-compose but I could reproduce this with docker itself.Expected outcome:
On a host without sysbox (and especially without usernsmap)
What I get with sysbox
I am a colleague of @nudgegoonies and we use a version with some patches from your side (concerning #266 etc.)
Same happens if I use
runc
. Maybe related touserns-remap
, see this moby-issue??The text was updated successfully, but these errors were encountered: