[Bug 925122] [NEW] container's udevadm trigger --add affects the host

[Serge Hallyn]

Public bug reported:

When the container does 'udevadm trigger --add' (in
/etc/init/udevtrigger.conf), the host re-processes all those events too.
This can lead (less importantly) to keyboard settings and soundcard
levels being reset, but (more importantly) could presumably also cause
worse troubles.

Once upstart has a concept of being ina  container, udev should be
updated to not run udevtrigger.conf when in a container.

** Affects: lxc (Ubuntu)
     Importance: Medium
         Status: Confirmed

** Affects: udev (Ubuntu)
     Importance: Medium
         Status: Confirmed

** Changed in: lxc (Ubuntu)
       Status: New => Confirmed

** Changed in: lxc (Ubuntu)
   Importance: Undecided => Medium

** Also affects: udev (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: udev (Ubuntu)
       Status: New => Confirmed

** Changed in: udev (Ubuntu)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to udev in Ubuntu.
https://bugs.launchpad.net/bugs/925122

Title:
  container's udevadm trigger --add affects the host

Status in “lxc” package in Ubuntu:
  Confirmed
Status in “udev” package in Ubuntu:
  Confirmed

Bug description:
  When the container does 'udevadm trigger --add' (in
  /etc/init/udevtrigger.conf), the host re-processes all those events
  too.  This can lead (less importantly) to keyboard settings and
  soundcard levels being reset, but (more importantly) could presumably
  also cause worse troubles.

  Once upstart has a concept of being ina  container, udev should be
  updated to not run udevtrigger.conf when in a container.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/925122/+subscriptions