Thanks Antonio for the clarify.

A side question: For docker test shell, if possible add more docker options for user? E.g. bind mount, etc.

A scenario is: If we have some code needed when test, currently, we could just inject it into docker image when do docker build, or when test git clone the code from network. You know docker test shell use `--rm`, means every time, we need to git clone it, or if a small changes we need to build the image. A bind mount there to mount our code may make things easier for us?

-----Original Message----- From: Lava-users lava-users-bounces@lists.lavasoftware.org On Behalf Of lava-users-request@lists.lavasoftware.org Sent: Saturday, June 6, 2020 8:00 PM To: lava-users@lists.lavasoftware.org Subject: [EXT] Lava-users Digest, Vol 22, Issue 7

Caution: EXT Email

Send Lava-users mailing list submissions to lava-users@lists.lavasoftware.org

To subscribe or unsubscribe via the World Wide Web, visit https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.lava... or, via email, send a message with subject or body 'help' to lava-users-request@lists.lavasoftware.org

You can reach the person managing the list at lava-users-owner@lists.lavasoftware.org

When replying, please edit your Subject line so it is more specific than "Re: Contents of Lava-users digest..."

Today's Topics:

1. Re: [EXT] Re: docker shell cannot handle adbd. (Antonio Terceiro)

----------------------------------------------------------------------

Message: 1 Date: Fri, 5 Jun 2020 09:26:18 -0300 From: Antonio Terceiro antonio.terceiro@linaro.org To: lava-users@lists.lavasoftware.org Subject: Re: [Lava-users] [EXT] Re: docker shell cannot handle adbd. Message-ID: 20200605122618.GA359587@linaro.org Content-Type: text/plain; charset="us-ascii"

On Fri, Jun 05, 2020 at 07:06:16AM +0000, Larry Shen wrote:

Hi, Milosz,

Maybe I understand wrong, but I already see there is code like next to add dynamic device node to docker container.

I tried it in manual, adb find devices after a new device node added with next code. But I don't see the docker shell try to call it with some way. What's the aim of next code if you did not want to use it? Could you double confirm internal maybe some guys is handling it, but just in process? Could you do me a favor inform me your plan if my guess is true?

I don't think people could switch from lxc to docker on android if this not support, maybe my environment wrong or anything else?

Yes, you are right. The way the docker test shell currently works won't support such a use case.

First, there was an issue with the udev rules being too strict, which was recently fixed and will be in the next release: https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.lavaso...

This issue that you mention also needs to be fixed; I created an issue to track and I will work on it: https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.lavaso...