Christian Brauner
Christian Brauner
> > FTR, I was playing around with that a few weeks ago, and so far I couldn't make it work -- writing back the received uevents without SEQNUM into...
And you need to keep in mind that uevents have a particular format where each property is '\0' separated.
In your code is `UEVENT_SEND` actually raised when writing into the socket? ```c #ifndef UEVENT_SEND #define UEVENT_SEND 16 #endif ``` in `nlmsg_type`?
> I pushed my initial experiment to https://github.com/martinpitt/uevent-container-forwarder . It does not actually work. I tried to run this all inside the container (as container user root) -- after all,...
(a) network namespace owned by initial user namespace -> receive all uevents (b) network namespace owned by a non-initial usernamespace (unshare(CLONE_NEWUSER | CLONE_NEWNET)) -> no uevents apart from network devices...
> I ran into this issue before and ended up figuring out that messages are only send to netns owned by the root userns. What I See above. > didn't...
> > Network devices are properly namespaced is what I said. > > Yeah, I got that. I wondered why events from some devices are restricted to netns belonging to...
Afaik, this is expected behavior. Config lines override each other in the order they are specified in.
Closing as this is expected behavior.
Oh wait, maybe I misunderstood you. Are you saying that one single call to: ``` container.set_config_item('lxc.cgroup.memory.memsw.limit_in_bytes', memsw_limit) ``` will set two lines in the container's config file?