Hi Neil,
When LAVA start container from image for the first time(usually docker run ), if failed, it will bring a zoobie container.
And I found that LAVA did not check whether LAVA run is OK, and has no dead container cleanup method.(maybe I was wrong).
Does LAVA have some method to prevent it or do you think it is necessary?
Best Regards
Li Xiaoming
On Tue, 20 Nov 2018 at 13:25, Li, Xiaoming lixm.fnst@cn.fujitsu.com wrote:
Hi Neil,
I'm not the only one to reply on this list. Please make sure you include all relevant information. If at all possible include links to the LAVA test job logs and device configuration or attach the full test job log to your email, as downloaded from the job link. Make sure you include the version of LAVA you are running and the output of any of the commands you describe.
When LAVA start container from image for the first time(usually docker run ), if failed, it will bring a zoobie container.
Which container are you using? What commands are you using to start it? Is this a docker test job using the docker device-type or a docker instance?
https://lava.codehelp.co.uk/scheduler/job/3997
And I found that LAVA did not check whether LAVA run is OK, and has no dead container cleanup method.(maybe I was wrong).
Do you mean that there is a docker image listed in the docker output? Which output?
Does LAVA have some method to prevent it or do you think it is necessary?
Depends - I'm not sure what the question is at the moment.
Best Regards
Li Xiaoming
Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users
lava-users@lists.lavasoftware.org