Hello,

What you're describing should be possible with the support of our official docker-compose yaml.
I encourage you to read through this part of the readme file https://git.lavasoftware.org/lava/pkg/docker-compose#configuration-advanced-for-physical-dut-purposes

The way our docker-compose works is that exposes the ports of the nfs and tftp to the outside of the host so there's no problem in the communication between DUT and those services (including the lava-dispatcher). You should pay special attention to the part of the readme regarding `dispatcher_ip` setting in the worker configuration.

In the end, you can paste some error logs for me and I can hopefully help you get to the bottom of your problem.

HTH,

On 2/20/20 4:08 PM, admirer mishra wrote:

Hi there,

Yesterday, while going through the mail, I found about the docker-compose file provided by lava. The script is amazing it gives even more understanding of how actual lava-server and dispatcher work. I am a complete beginner just working on lava and docker from last 20 days.

So, I am trying to boot a x86 device via ipxe using nfs and tftp protocol. In normal lava server running on host everything works fine because the host ip and target ip are on same local network so tftp and nfs works fine. But docker uses internal network and target is on local network so how to configure so that it works?

I also used the docker compose file but the problem still persists. Is there any other configuration in the containers that I have to do make it work? Please help I am complete newbie in this field.

Thanks for your time

admirer mishra
_______________________________________________
Lava-users mailing list
Lava-users@lists.lavasoftware.org
https://lists.lavasoftware.org/mailman/listinfo/lava-users

-- 
Stevan Radaković | LAVA Engineer
Linaro.org <www.linaro.org> │ Open source software for ARM SoCs