Description of problem: udev events are not available inside of an SPC (super privileged container), but some components (like vdsm from RHEV) require those events to work correctly. We need a way to retrieve the udev events inside the container. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. run any SPC 2. On the host run udevadm monitor --udev --env 3. In the container run udevadm monitor --udev --env 4. On the host run udevadm trigger --action=change --subsystem-match=block Actual results: udevadm on the host shows the udev events udevadm in the container does not show the udev events Expected results: udevadm in the container shows the udev events Additional info:
Time has passed. A nice way to get custom udev rules onto the host might be, to use LABELs to name the udev rules which should be copied frmo the container onto the host. I.e. LABEL org.storaged.udev.rules /etc/…/foo.rule This rule would be copied to the host each time a new image is deployed. This drops the burden from the image/container to move the rule to the right place. There is just a component needed on the host side to perform this acton. This idea actually comes from cadvisor who is using labels to expose config files inside a container. In addition: By dropping most namespaces and bindmounting /runevents should get inside of a container.