On Fri, Feb 12, 2016 at 04:37:48PM -0000, Stéphane Graber wrote: > Yeah, I've seen that before, we need to figure out why apt even attempts > a restart when lxd isn't running (and in this case, can't run) to begin > with. > > If you want LXD to be able to start inside a container, the container > must have security.nesting set to true.
I didn't even really need it inside a container. It just happened to be there and get dist-upgraded because it is seeded. If this causes a problem, then can we detect that somehow automatically, so it doesn't affect anyone who ended up with it by "accident" through the seed? (this might be what you meant already, I'm not sure) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1545017 Title: dist-upgrading xenial hangs in lxd.postinst To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1545017/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
