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
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".
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?
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
Hi, Neil,
Two questions:
1. With external ip set in dispatcher.d is the recommended way to use lava dispatcher docker? You can notice: I have set up "--net=host" when start container, and tftp download just ok, just ntp cannot start. My worker's ip is jsut same as host's ip as I did not use "docker0", I share the network namespace of host.
2. If I follow your suggestion to use external ip, then I wonder: how to configure it in dispatcher.d, there is not any configure file in the folder /etc/lava-server/dispatcher.d
Please suggest, thanks. ------------------------------------------------------------------ 发件人：Neil Williams neil.williams@linaro.org 发送时间：2019年2月19日(星期二) 18:53 收件人：cnspring2002 cnspring2002@aliyun.com 抄 送：lava-users lava-users@lists.lavasoftware.org 主 题：Re: [Lava-users] lava in docker.
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
On Wed, 20 Feb 2019 at 02:06, cnspring2002 cnspring2002@aliyun.com wrote:
Hi, Neil,
Two questions:
- With external ip set in dispatcher.d is the recommended way to use lava dispatcher docker?
You can notice: I have set up "--net=host" when start container, and tftp download just ok, just ntp cannot start. My worker's ip is jsut same as host's ip as I did not use "docker0", I share the network namespace of host.
Recommendations for docker with LAVA are here: https://master.lavasoftware.org/static/docs/v2/docker-admin.html#index-0
Specifically networking: https://master.lavasoftware.org/static/docs/v2/docker-admin.html#docker-netw...
A docker network is recommended, this will generate a different IP for each container, allowing more than one container to be run on the same host.
- If I follow your suggestion to use external ip, then I wonder: how to configure it in dispatcher.d, there is not any configure file in the folder /etc/lava-server/dispatcher.d
https://master.lavasoftware.org/static/docs/v2/pipeline-admin.html#extra-dis...
"An example file exists in /usr/share/lava-dispatcher/dispatcher.yaml on each worker."
Please suggest, thanks.
发件人：Neil Williams neil.williams@linaro.org 发送时间：2019年2月19日(星期二) 18:53 收件人：cnspring2002 cnspring2002@aliyun.com 抄 送：lava-users lava-users@lists.lavasoftware.org 主 题：Re: [Lava-users] lava in docker.
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
--
Neil Williams
neil.williams@linaro.org http://www.linux.codehelp.co.uk/
lava-users@lists.lavasoftware.org
-
cnspring2002 -
Neil Williams