Hello Milosz,

Le dim. 24 févr. 2019 à 11:43, Milosz Wasilewski <milosz.wasilewski@linaro.org> a écrit :
On Tue, 19 Feb 2019 at 10:10, Remi Duraffort <remi.duraffort@linaro.org> wrote:
>
> Hello Milosz,
>
> I've been also playing with LAVA docker containers and docker-compose. I now provide a docker-compose.yaml file and some configuration files for lava-server at http://git.lavasoftware.org/lava/pkg/docker-compose/
> This docker-compose files allows to run lava server services with each services running in is own container.

what is the difference between lava-server and lava-master in your
example? Also why apache2 container uses LAVA image not httpd image?

lava-server is the gunicorn process serving the html pages
lava-master is the scheduler and master process (master as in master <-> slave)

apache2 is serving static files (lava css, js, ...) that are coming from the lava-server image. Maybe there is a better way?


Cheers

-- 
Rémi Duraffort
LAVA Team, Linaro