On Thu, 7 Feb 2019 at 08:02, tomato seoji@nexell.co.kr wrote:
Hi. I encountered a problem running android apk test.
I tried to run Antutu apk-automation test on android device.
This is log created when test job create and run lxc container.
start: 1 lxc-deploy (timeout 00:05:00) [tlxc]start: 1.1 lxc-create-action (timeout 00:05:00) [tlxc]nice lxc-create -q -t debian -n s5p4418-test-46 -- --release jessie --packages systemd,systemd-sysv --arch amd64Container created successfullyend: 1.1 lxc-create-action (duration 00:00:30) [tlxc]case: lxc-create-action case_id: 541 definition: lava duration: 29.74 extra: ... level: 1.1 namespace: tlxc result: pass http://192.168.1.44/results/testcase/541start: 1.2 lxc-create-udev-rule-action (timeout 00:04:30) [tlxc]device info file '/var/lib/lava/dispatcher/tmp/46/lxc-create-udev-rule-action-ymvjdkgm/device-info.yaml' created with: [{'board_id': 's5p4418-navi-ref'}]udev rules file '/var/lib/lava/dispatcher/tmp/46/lxc-create-udev-rule-action-muvnvu7f/100-lava-s5p4418-test-46.rules' createdACTION=="add", ATTR{serial}=="s5p4418-navi-ref", RUN+="/usr/share/lava-dispatcher/lava_lxc_device_add.py --lxc-name s5p4418-test-46 --device-node $name --job-id 46 --logging-url tcp:// 192.168.1.44:5557" '/etc/udev/rules.d/100-lava-s5p4418-test-46.rules' symlinked to '/var/lib/lava/dispatcher/tmp/46/lxc-create-udev-rule-action-muvnvu7f/100-lava-s5p4418-test-46.rules'nice udevadm control --reload-rulesaction: lxc-create-udev-rule-action command: ['nice', 'udevadm', 'control', '--reload-rules'] message: Command '['nice', 'udevadm', 'control', '--reload-rules']' returned non-zero exit status 2 output: Command '['nice', 'udevadm', 'control', '--reload-rules']' returned non-zero exit status 2 udev rules reloaded.end: 1.2 lxc-create-udev-rule-action (duration 00:00:00) [tlxc]start: 1.3 boot-lxc (timeout 00:04:30) [tlxc]nice lxc-start -n s5p4418-test-46 -daction: boot-lxc command: ['nice', 'lxc-start', '-n', 's5p4418-test-46', '-d'] message: Command '['nice', 'lxc-start', '-n', 's5p4418-test-46', '-d']' returned non-zero exit status 1 output: lxc-start: tools/lxc_start.c: main: 366 The container failed to start. lxc-start: tools/lxc_start.c: main: 368 To get more details, run the container in foreground mode. lxc-start: tools/lxc_start.c: main: 370 Additional information can be obtained by setting the --logfile and --logpriority options. Wait until 's5p4418-test-46' state becomes RUNNINGnice lxc-info -sH -n s5p4418-test-46output: STOPPEDoutput: nice lxc-info -sH -n s5p4418-test-46output: STOPPEDoutput:
I wonder if it is okay to create and run lxc container in docker container.
LXC does not operate inside Docker. You need to install the lav-lxc-mocker package inside the docker (the official docker images already have it installed) to prevent LXC operations being attempted.
https://packages.debian.org/unstable/lava-lxc-mocker
Which Docker image are you using? In future, please attach the FULL logs and avoid pasting the content into the body of the email. Use the download link to get the YAML which contains additional information like the timestamps.
We do not yet have fully working examples of driving android devices in LAVA from Docker. At this point, I would recommend that you do not attempt to run android test jobs using a LAVA worker running inside Docker. You will need to install lava-dispatcher on a Debian system, as we currently use for all android test jobs.