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

[Michael Biebl]

Am 02.09.2019 um 00:30 schrieb Michael Biebl:
> Control: reassign -1 lxc
> 
> Am 01.09.2019 um 23:31 schrieb Sergey Aleynikov:
>> Source: systemd
>> Version: 241-5
>> Severity: important
>>
>> Dear Maintainer,
>>
>> *** Reporter, please consider answering these questions, where appropriate ***
>>
>>    * What led up to the situation?
>> I'm running LXC containers (lxc version 1:2.0.7-2+deb9u2) on debian stretch. I have several containers
>> with different debian versions inside. After I've done stretch->buster upgrade in one of them, it stopped
>> working with 'lxc-start: tools/lxc_start.c: main: 366 The container failed to start.' message.
>>
>>    * What exactly did you do (or not do) that was effective (or
>>      ineffective)?
>>
>> This is a reproducible sequence:
>>
>> lxc-create -n testupg -t download # choose debian - stretch - amd64
>> lxc-start -n testupg
>> lxc-attach -n testupg
>> # inside container
>> vi /etc/apt/sources.list # change stretch -> buster
>> apt-get update
>> apt-get dist-upgrade
>> exit
>> # outside of container
>> lxc-stop -n testupg
>> lxc-start -n testupg # won't work
>>
>> I'd expect containers to keep working after dist-upgrade.
> 
> Let's reassign that to lxc then. I don't see anything systemd specific here.

Especially since you seem to be using sysvinit.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-lxc-devel/attachments/20190902/e6c8365d/attachment.sig>