* Re: [Lava-users] What's the difference between kernel ci's docker and official docker?
2019-04-25 7:21 ` [Lava-users] What's the difference between kernel ci's docker and official docker? Milosz Wasilewski
@ 2019-04-29 21:48 ` Kevin Hilman
0 siblings, 0 replies; 2+ messages in thread
From: Kevin Hilman @ 2019-04-29 21:48 UTC (permalink / raw)
To: kernelci, milosz.wasilewski, Larry Shen; +Cc: lava-users@lists.lavasoftware.org
"Milosz Wasilewski" <milosz.wasilewski@linaro.org> writes:
> +kernelci
>
> On Thu, 25 Apr 2019 at 03:33, Larry Shen <larry.shen@nxp.com> wrote:
>>
>> Hi,
>>
>>
>>
>> I’d like to know is this site official? https://github.com/kernelci/lava-docker
>>
>
> This is the 1st historical implementation. At the time KCI created
> docker container there were no containers coming from LAVA project.
Correct.
>>
>> Does this project same as the one in dockerhub, lavasoftware/lava-server?
>
> I'm not exactly sure what the differences are between kernelci and
> official LAVA containers. I suspect the might at least differ when it
> comes to the version of LAVA release inside.
> lavasoftware/lava-{server,dispatcher} are official containers provided
> by LAVA project.
The kernelCI docker images have 2 parts
1) the base LAVA images
2) kernelCI specific customizations
For (1), we're currently building our own images, but are planning to
switch to the official ones supplied by the lavasoftware dockerhub.
The only reason we have our own is because these didn't exist when we
started doing docker images.
For (2), there's all sorts of stuff we're doing for the lava-docker
project that is not directly related to LAVA. In particular, we're
providing an abstraction for describing your master/slave configuration
and DUTs via a YAML config file, so you really don't have to know
anything about LAVA. All of that is lava-docker specific, and out of
the scope of what the lavasoftware dockerhub would provide.
For all the details on (2), see the main README here:
https://github.com/kernelci/lava-docker/
Kevin
^ permalink raw reply [flat|nested] 2+ messages in thread