Hi,
I was recently asked to prepare a docker compose that includes both LAVA and SQUAD. This was fairly easy (a few hurdles with LAVA master, but nothing serious). Currently I have a setup that has SQUAD parts in separate containers, and LAVA master in separate. SQUAD connects to LAVA using docker network. This unfortunately causes incorrect URLs produced nu LAVA backend in LAVA are incorrect. They point to internal docker addresses and are not accessible from outside. To give the proper example: - LAVA master runs in a container named lava-master. It listens on ports 8000 (http) and 5555 (zmq) - SQUAD has backend configures with LAVA url as http://lava-master:8000/RPC2
The result is that metadata in SQUAD builds show job URLs as http://lava-master:8000/scheduler/job/<job id>. Obviously this URL isn't available from the host network. If I configure backend to use host's network URL it won't be able to connect. At least I don't know how to make this happen. Does anyone have any idea how to fix it? Is there a way for docker encapsulated apps to communicate using host's network? Here is a link to my docker-compose: https://github.com/mwasilew/lite-lava-docker-compose/blob/lite/docker-compos...
milosz