Bug#766233: VM won't start after an automatic upgrade to systemd inside the VM

Antonio Terceiro terceiro at debian.org
Tue Oct 28 16:59:40 GMT 2014


Control: severity 766216 important

On Wed, Oct 22, 2014 at 11:01:36AM +0200, Holger Levsen wrote:
> 3. jessie host with jessie lxc containers (=does work with systemd in the 
> container)

This does not work in my experience (reported as #766216), so at the
moment is not possible to run jessie containers that run systemd on
jessie, also running systemd. I don't know if running sysvinit in the
host would help.

I also had problems with a CentOS 7 container; the issue looks like the
one reported in
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1339781

However, in my case removing the drop of SETFCAP in centos.common.conf
did not help.

-- 
Antonio Terceiro <terceiro at debian.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20141028/0e719e51/attachment-0002.sig>


More information about the Pkg-systemd-maintainers mailing list