-----Original Message----- From: Antonio Terceiro antonio.terceiro@linaro.org Sent: 19 August 2020 13:19 To: Stephen Lawrence stephen.lawrence@renesas.com Cc: lava-users@lists.lavasoftware.org Subject: Re: fastboot reboot-bootloader from docker test shell (was "fastboot in docker support")
[snip]
lava-dispatcher-host needs to be installed and configured (i.e. udev rules in place) on the host system for it to work, exactly because udev events are not (and probably should not be) available inside the container.
Hi Antonio, thanks for the input. I'll continue to use lava-dispatcher-host on the host then.
This then goes back to the first question I raised yesterday about how the lava devs see udev discovery commonly working when LAVA is containerised. For example, whether it happens on the host and is somehow communicated into the worker container, or whether 'full' udev is required in the worker container or whether in some cases a different setup is possible. I'll report on the last choice below.
Running the dispatcher in a container and still being able to run jobs inside containers is still WIP from our PoV, I am only now starting to look at it.
I added one recent gotcha when running in a container as a comment to Paul's docker issue on gitlab, but it was not the perfect home for it. Paul's issue is more specific I think.
Anyway as you get further into it and if it it's a help to hear what problems ppl hit doing it then feel free to ask or point at where to add them.
Regards
Steve