On Tue, 19 Feb 2019 at 09:53, cnspring2002 cnspring2002@aliyun.com wrote:
I use next command to start lavadispatcher:
docker run -idt --net=host --privileged -v /dev:/dev -v /var/lib/lava/dispatcher/tmp:/var/lib/lava/dispatcher/tmp -e "DISPATCHER_HOSTNAME=--hostname=myname" -e "LOGGER_URL=tcp://master_ip:5555" -e "MASTER_URL=tcp://master_ip:5556" --name test_lava lavasoftware/lava-dispatcher:2019.01
There is ongoing development in this area.
In container, I start tftp and nfs. But the nfs always cannot be start successfully. I use "service nfs-kernel-server start" to start it, also before that I did "rpcbind".
You should run tftp and NFS outside the docker - the added volume will pick up the files created by lava-run inside the docker. You will need a dispatcher.d configuration file for this worker on the master to set the dispatcher_ip to the external IP address, not the IP address of the worker.
The start shows below seems ok: # service nfs-kernel-server start [ ok ] Exporting directories for NFS kernel daemon.... [ ok ] Starting NFS kernel daemon: nfsd mountd.
But if do next we can see the nfs still not start. # service nfs-kernel-server status nfsd not running
Any suggestion? _______________________________________________ Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users