[pkg-lxc-devel] Bug#939168: systemd: LXC container fails to start after stretch->buster update inside container

Sergey Aleynikov sergey.aleynikov at gmail.com
Mon Sep 2 20:10:52 BST 2019

> You should probably attach the output of
> reportbug --template lxc
> to this bug report so the lxc maintainers have some context.

I'm attaching 'lxc-start -n testupg --logfile=lxc.log -l DEBUG' and
'reportbug --template lxc' outputs to this message.

> Checking the existing bug reports, there are already a few which concern
> sysvinit.
> I would suggest that you check them out like
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869892

I've looked at them yesterday, just in case, and didn't see anything
obviously related. For example, for this one, I already have
cgroupfs-mount installed and /sys/fs/cgroup present. And while I see
mounting errors for the container after upgrade (not the attached log,
but the original container i've tried to upgrade), they do not seem to
be an immediate cause for the startup failure.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lxc.log
Type: application/octet-stream
Size: 18391 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-lxc-devel/attachments/20190902/4b7e663d/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: reportbug.log
Type: application/octet-stream
Size: 2225 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-lxc-devel/attachments/20190902/4b7e663d/attachment-0003.obj>

More information about the Pkg-lxc-devel mailing list