Finally some time to check more.
Using new /etc/init/lxc-android-config.conf from Stephane
http://paste.ubuntu.com/15264484/
When running manually $ lxc-start -n android -F -- /init
I can see init process be created, but then it exits. Also there are no logs in
syslog or /proc/kmesg
So looks like init is super unhappy inside the container and does not do much.
But because it actually tries to run, following passes fine
lxc-wait -n android -s RUNNING -t 30
containerpid="$(lxc-info -n android -p -H)"
if [ -n "$containerpid" ]; then
and tries to continue with boot, while container actually fails to boot.
Is there way we can get more logs from running container, I tried this:
lxc-start -l 0 -n android -F -- /init
rm: cannot remove '/var/lib/lxc/android/rootfs/sbin/adbd': No such file or
directory
run-parts: /var/lib/lxc/android/pre-start.d/10-no-adbd exited with return code 1
sed: can't read /var/lib/lxc/android/rootfs/init.manta.usb.rc: No such file or
directory
cp: cannot stat '/var/lib/lxc/android/overrides/*': No such file or directory
mkfifo: cannot create fifo '/dev/socket/micshm': File exists
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1551150
Title:
devel-proposed - android lxc container fails to start
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
