Hello,

is the configuration file (/etc/lava-server/dispatcher.d/<hostname>/dispatcher.yaml) visible from the master container?

In the docker-compose setup, each service is running in a specific container so the configuration files should be set carefully.

Rgds

Le mar. 19 nov. 2019 à 09:25, Klaas Schulze-Dieckhoff < K.Schulze-Dieckhoff@sonnen.de> a écrit :

Hi all,

I am running lava using docker-compose. Additional to the official docker-compose.yaml I added and FTP and NFS container. For testing my setup I am trying to test a beaglebone black.

In order to load dtb and kernel uboot needs to know the IP of the FTP / NFS server. I added the IP in the following two ways:

server:

root@1a010c2f736b:/# cat /etc/lava-server/dispatcher.d/lava-dispatcher.yaml

dispatcher_ip: <server ip addr>

dispatcher:

root@075e2deb4c34:/# cat /etc/lava-dispatcher/lava-slave

[....]

NFS_SERVER_IP="<server-ip-addr> "

The hostname of the dispatcher is `lava-dispatcher`. But, when the health-check is running it will always run `setenv serverip <ip-of-docker-container>.

I also tried various variants of setting the dispatcher configuration (./dispatcher.d/<hostname>/dispatcher.yaml, ./dispatcher.d/<hostname>/env.yaml). No matter what I do lava persists to take the IP of the docker-container.

According to ` server/management/commands/lava-master.py` line 465 at least one of the variants should word,

I would appreciate some hints how to fix this!

Thanks Klaas

Geschäftsführer: Christoph Ostermann (CEO), Oliver Koch, Steffen Schneider, Hermann Schweizer, Tim Ulbricht. Amtsgericht Kempten/Allgäu, Registernummer: 10655, Steuernummer 127/137/50792, USt.-IdNr. DE272208908 _______________________________________________ Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users