Thanks. I think the problem is a newly introduced check for path
writeability which is harmless and in fact, potentially useful in just
about all cases but the weird Ubuntu Phone case where / is read-only,
confusing that check.
@Christian: Can you look into fixing this? I suspect we only really care
about being able to access the path, not so much about being able to
write to it. So it may make sense to change the check in all our tools
to simply check for read rights.
** Changed in: lxc (Ubuntu)
Assignee: (unassigned) => Christian Brauner (cbrauner)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1653725
Title:
lxc-android-config not starting on ubuntu-touch/staging/* xenial-based
images after lxc upgrade
Status in Canonical System Image:
Confirmed
Status in lxc package in Ubuntu:
New
Status in lxc-android-config package in Ubuntu:
New
Bug description:
As in topic. Since the 20161217 rootfs, after upgrade of lxc from
2.0.5-0ubuntu1~ubuntu16.04.3 to 2.0.6-0ubuntu1~ubuntu16.04.1 the lxc-
android-config service does not start - making the devices unbootable.
The syslog only states this:
Jan 3 10:50:30 ubuntu-phablet systemd[1]: Starting LXC Android Config and
Container Initialization...
Jan 3 10:50:30 ubuntu-phablet kernel: [ 5.790810] (3)[1:systemd]SLEEP_EN
= 0x1
Jan 3 10:50:30 ubuntu-phablet systemd[1]: Starting Light Display Manager...
Jan 3 10:50:30 ubuntu-phablet systemd-udevd[672]: Could not generate
persistent MAC address for ifb0: No such file or directory
Jan 3 10:50:30 ubuntu-phablet systemd-udevd[684]: Could not generate
persistent MAC address for ifb1: No such file or directory
Jan 3 10:50:30 ubuntu-phablet lxc-start[1220]: You lack access to
/var/lib/lxc
Jan 3 10:50:30 ubuntu-phablet systemd[1]: lxc-android-config.service:
Control process exited, code=exited status=1
Jan 3 10:50:30 ubuntu-phablet systemd[1]: Failed to start LXC Android Config
and Container Initialization.
Jan 3 10:50:30 ubuntu-phablet systemd[1]: Dependency failed for
force-mtp.service.
Jan 3 10:50:30 ubuntu-phablet systemd[1]: force-mtp.service: Job
force-mtp.service/start failed with result 'dependency'.
Jan 3 10:50:30 ubuntu-phablet systemd[1]: lxc-android-config.service: Unit
entered failed state.
Jan 3 10:50:30 ubuntu-phablet systemd[1]: lxc-android-config.service: Failed
with result 'exit-code'.
This makes all of our frieza and cooler devices useless for testing
purposes.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1653725/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
