On May 9, 2019, at 8:11 AM, Kumar Gala kumar.gala@linaro.org wrote:

In trying to run lava-dispatcher inside a docker container and connect a FRDM-K64F board ran into some issues related to the fact that udev events aren’t seen inside the container since we aren’t typically running systemd/udevd there.

I came across this project that will forward udev events from the host to a container that worked pretty well:

https://github.com/eiz/udevfw

I’ve re-implemented this in python for easier development (added some docker awareness):

https://git.lavasoftware.org/galak/docker-compose/blob/lite/contrib/udev-for...

Right now running udev-forward.py is kinda kludgy. Wanted to get input on how people think this should work, should we make a daemon out of it? Should there be some kinda of config file? Do we think we need to filter events (and if so how)? Need to look at support for multicasting (support sending to multiple dispatchers). Where should this live, in docker-compose repo?

Other thoughts.

• k

I’ve updated my udev-forward.py script to handle multicasting and handle the lifecycle of docker containers better (having them come up/down, already be running).

Now its much closer to being able to run just as a deamon, still need to figure out how we’d specify config info for that case.

- k