On Wed, 22 Oct 2014, Holger Levsen wrote:

ain't there a 5th option, providing an lxc 1.0.x backport for jessie?

You mean a backport to wheezy? Beacause the problem seems to be that if a pre-1:1.0.6-3 (as in wheezy) lxc starts a jessie container that's using systemd, then that wheezy lxc won't be able to run systemd in a correct way.

[email protected] has one prepared on mentors.d.n but I was reluctant to sponsor it
(so far) as it was only 1.0.5-x, while 1.0.6-1 just had hit sid...

But a backport should fix this issue, possible in combination with a newer
kernel from backports.

This seems like the best solution to me. Given that only a few months (how many?) seem to be remaining until release - is it feasible in that time frame to have 1.0.6-3 migrate from unstable to tesing and at the same time have it either included in an lxc point release for wheezy or in wheezy-backports?

What do you think about this solution Daniel?

And yes, documenting this issue in the release notes would be good
anyway/also! ;-)

I can do that, however I think it'd be good to know beforehand how this problem will be tackled, so I can document the possible solutions.
*t


--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to