On Fri, Jul 10, 2020 at 06:28:35PM +0000, Stephen Lawrence wrote:
Hi Antonio,
-----Original Message----- From: Antonio Terceiro antonio.terceiro@linaro.org Sent: 06 July 2020 13:04 To: Stephen Lawrence stephen.lawrence@renesas.com Cc: lava-users@lists.lavasoftware.org; gandersson@genivi.org Subject: Re: [Lava-users] fastboot in docker support
[snip]
Antonio wrote:
FWIW they are up in merge request 1238: https://git.lavasoftware.org/lava/lava/-/merge_requests/1238
I am running the changes by updating to the 2020.07 Linaro docker image.
I found that in the simple case my jobs will now execute the docker container, e.g: https://lava.genivi.org/scheduler/job/1047
but when I do any actual fastboot work from the container the host waits for the device and eventually times out, e.g: https://lava.genivi.org/scheduler/job/1048#L245
I notice that no device is passed in the docker run. Is that expected behaviour?
It is now. the device is not not passed in the docker run command line, but shared with the container dynamically via lava-dispatcher-host either right at the beginning, or whenever the device appears to udev.
I need to investigate further Monday but I wanted to ask if your udev changes bring any new requirements to device configuration such as device or device-type templates?
You should not need any changes to the device config.
You said you are running the dispatcher in docker; how exactly are you doing that? For docker to work for this from a dispatcher running inside docker, you need:
- lava-dispatcher-host installed and configured on the host OK - /var/lib/lava/dispatcher/tmp and /run/udev from the host OS bind mounted in the dispatcher container - the docker socket from the host OS shared with the dispatcher containers, so that the containers started by the dispatcher are siblings of the dispatcher container and not its children.
Does that make sense? I have it on my TODO list to properly document this for the next release, hopefully I will be able to do it in a more comprehensible way.