Retitling the bug to be more general, and adding a trusty task to
reflect the original "trusty host" part. This was discussed on UOS last
week (https://blueprints.launchpad.net/ubuntu/+spec/core-1411-systemd-
migration). The intention is to make this work on vivid first, and then
backport a newer LXC (or possibly just some patches) to trusty so that
systemd containers work on trusty as well.
** Summary changed:
- trusty host - utopic lxc container cloudimage boot with systemd does not work
+ systemd does not boot in a container
** Also affects: lxc (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: lxc (Ubuntu Trusty)
Status: New => Triaged
** Changed in: lxc (Ubuntu)
Status: Confirmed => Triaged
--
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/1347020
Title:
systemd does not boot in a container
Status in “lxc” package in Ubuntu:
Triaged
Status in “lxc” source package in Trusty:
Triaged
Bug description:
Opening against cloud-init for now, but ultimately might end up as
bug-fixes / srus against some other packages in trusty.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1347020/+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
