so I did use new script for LXC
Now I can see that Android init process is started but it fails quite soon,
with not much logs indicating actual issue.
This is just speculation, but probably still issue how /proc and /dev are
mounted to container?
Here are all the logs I get from Android init:
Jan 1 02:02:38 ubuntu-phablet kernel: [ 10.107370] init: cannot find
'/system/etc/install-recovery.sh', disabling 'flash_recovery'
Jan 1 02:02:38 ubuntu-phablet kernel: [ 10.107523] init: cannot find
'/system/bin/ubuntuappmanager.disabled', disabling 'ubuntuappmanager'
Jan 1 02:02:38 ubuntu-phablet kernel: [ 10.112345] binder: 1064:1064
transaction failed 29189, size 0-0
Jan 1 02:02:38 ubuntu-phablet dbus[862]: [system] Successfully activated
service 'org.freedesktop.login1'
Jan 1 02:02:38 ubuntu-phablet kernel: [ 10.190172] pil pil4: gss: Failed
to locate gss.mdt
Jan 1 02:02:38 ubuntu-phablet kernel: [ 10.214710] pil pil4: gss: Failed
to locate gss.mdt
Jan 1 02:02:38 ubuntu-phablet kernel: [ 10.220051] pil pil4: gss: Failed
to locate gss.mdt
Jan 1 02:02:38 ubuntu-phablet kernel: [ 10.231191] pil pil4: gss: Failed
to locate gss.mdt
Jan 1 02:02:38 ubuntu-phablet kernel: [ 10.243003] init: using
deprecated syntax for specifying property 'ro.serialno', use ${name} instead
Jan 1 02:02:38 ubuntu-phablet kernel: [ 10.243277] init: using
deprecated syntax for specifying property 'ro.product.manufacturer', use
${name} instead
Jan 1 02:02:38 ubuntu-phablet kernel: [ 10.243552] init: using
deprecated syntax for specifying property 'ro.product.model', use ${name}
instead
Jan 1 02:02:38 ubuntu-phablet kernel: [ 10.250572] usbcore: registered
new interface driver rmnet_usb
Jan 1 02:02:38 ubuntu-phablet kernel: [ 10.257042] rmnet usb ctrl
Initialized.
Jan 1 02:02:38 ubuntu-phablet kernel: [ 10.347413] init: property
'sys.powerctl' doesn't exist while expanding '${sys.powerctl}'
Jan 1 02:02:38 ubuntu-phablet kernel: [ 10.347627] init: powerctl:
cannot expand '${sys.powerctl}'
Jan 1 02:02:38 ubuntu-phablet kernel: [ 10.347840] init: property
'sys.sysctl.extra_free_kbytes' doesn't exist while expanding
'${sys.sysctl.extra_free_kbytes}'
Jan 1 02:02:38 ubuntu-phablet kernel: [ 10.348023] init: cannot expand
'${sys.sysctl.extra_free_kbytes}' while writing to
'/proc/sys/vm/extra_free_kbytes'
On Fri, Apr 15, 2016 at 2:25 PM, Łukasz Zemczak <1551...@bugs.launchpad.net>
wrote:
> Can we get some traction on this? devel-proposed has been unbootable for
> too long. With xenial going into Final Freeze it would be nice to get
> this working around release-time. In touch we're not following the
> standard Ubuntu cycles, but it would be nice to have a bootable baseline
> when using xenial.
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1551150
>
> Title:
> devel-proposed - android lxc container fails to start
>
> Status in Canonical System Image:
> Confirmed
> Status in lxc package in Ubuntu:
> Confirmed
>
> Bug description:
> Last known good image: ubuntu-touch/devel-proposed/ubuntu/mako 446
>
> ubuntu-touch/devel-proposed/ubuntu/mako 447 (and higher) and
> equivalent images on other devices do not boot and hang on the boot
> logo.
>
> From the list of changes, it could be lxc:
> 446: lxc 2.0.0~rc2-0ubuntu2
> 447: lxc 2.0.0~rc3-0ubuntu1
>
> Latest image with 2.0.0~rc4-0ubuntu1 doesn't boot either.
>
> lxc (2.0.0~rc3-0ubuntu1) xenial; urgency=medium
>
> * New upstream release (2.0.0~rc3)
> - Make the cgfs backend and cgns work without cgmanager
> - Manpage updates
> - Mark lxc-clone and lxc-start-ephemeral deprecated (still included)
> * Set --enable-deprecated so we still ship lxc-clone and
> lxc-start-ephemeral
>
> lxc (2.0.0~rc2-0ubuntu3) xenial; urgency=medium
>
> * Use versioned dependencies against the various binary packages.
> * Update lxc-templates to depend on lxc1 not lxc. (LP: #1549136)
> * Move the lxcfs recommends from lxc-templates to liblxc1.
> * Drop cgmanager, use the cgfs backend instead.
> * Have liblxc1 depend on systemd | cgroup-lite for cgfs backend.
>
> Device tarballs between 446 and 447 are the same.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+subscriptions
>
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
