Hi, Antonio,
I submit a MR: https://git.lavasoftware.org/lava/lava/-/merge_requests/1270 for extra bind mount of docker test shell, please have a look when you have time, thanks.
-----Original Message----- From: antonio.terceiro@linaro.org antonio.terceiro@linaro.org Sent: Monday, July 13, 2020 8:42 PM To: Larry Shen larry.shen@nxp.com Cc: lava-users@lists.lavasoftware.org Subject: Re: [EXT] Re: [Lava-users] docker shell cannot handle adbd.
On Thu, Jul 09, 2020 at 02:52:52AM +0000, Larry Shen wrote:
Hi, Antonio,
I see adbd restart support already ok in MR1238, thanks.
Meanwhile, I see an additional bind mount for "LAVA_DOWNLOADS", but it could not meet our requirements. So continue the question: if possible to add more bind mount for "docker test shell"?
Something like: Option 1: Let lab admin specify bind mounts in device.jinja2, then "docker test shell" could mount it?
Option 2: "docker test shell" always bind mount a static "callback location", if that "callback location" exists on host, mount it. Then users could just put the things in that "callback location". Looks this limited bind mount won't bring any risk to host machine?
You know, I'm talking about "big things like some code, pictures, videos etc" which not so efficiency to be download on the fly when test start. Meanwhile, don't want to generate docker image again and again once there is something change. So, bind mount is the most convenient solution for us.
Yes, I guess we could do that. I like your option 2 more: a fixed directory in the host (configurable, but fixed at runtime) that gets bind mounted at a also well known location inside test containers. Feel free to propose a MR.