On Tue, Mar 31, 2020 at 07:32:08PM +0530, koti koti wrote:
Thanks Milosz.
Still "adb devices" does list the devices in the docker even those were listed in host machine.
" root@0feacfced787:/opt# dpkg -i lava-common_2020.02.0143.gd20f3bc24+10+buster_all.deb (Reading database ... 24077 files and directories currently installed.) Preparing to unpack lava-common_2020.02.0143.gd20f3bc24+10+buster_all.deb ... Unpacking lava-common (2020.02.0143.gd20f3bc24+10+buster) over (2020.02.0143.gd20f3bc24+10+buster) ... Setting up lava-common (2020.02.0143.gd20f3bc24+10+buster) ...
root@0feacfced787:/opt# dpkg -i lava-dispatcher-host_2020.02.0143.gd20f3bc24+10+buster_all.deb (Reading database ... 24077 files and directories currently installed.) Preparing to unpack lava-dispatcher-host_2020.02.0143.gd20f3bc24+10+buster_all.deb ... Unpacking lava-dispatcher-host (2020.02.0143.gd20f3bc24+10+buster) over (2020.02.0143.gd20f3bc24+10+buster) ... Setting up lava-dispatcher-host (2020.02.0143.gd20f3bc24+10+buster) ...
root@0feacfced787:/opt# /etc/init.d/udev restart [ ok ] Stopping hotplug events dispatcher: systemd-udevd. [ ok ] Starting hotplug events dispatcher: systemd-udevd.
root@0feacfced787:/opt# adb devices List of devices attached
root@0feacfced787:/opt#
This is not suppposed to work. lava-dispatcher-host will interact with the dispatcher and give device accesst to containers that were started by the dispatcher, not to the container where the dispatcher itself is running.