container's udevadm trigger --add affects the host
Bug #925122 reported by
Serge Hallyn
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lxc (Ubuntu) |
Invalid
|
Medium
|
Unassigned | ||
udev (Ubuntu) |
Fix Released
|
Medium
|
Stéphane Graber |
Bug Description
When the container does 'udevadm trigger --add' (in /etc/init/
Once upstart has a concept of being ina container, udev should be updated to not run udevtrigger.conf when in a container.
Related branches
Changed in lxc (Ubuntu): | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in udev (Ubuntu): | |
status: | New → Confirmed |
importance: | Undecided → Medium |
To post a comment you must log in.
My guess is that juju is setting umask somewhere? The mode passed to mkdir(2) is &'d with the task's umask. The code in lxc definately passes 0755 as the mode. We could patch lxc to do an explicit chmod after the fact, but that seems like the wrong thing to do. The umask - ideally - was set as it was for a reason.