[lxc-users] Containers won't start under stretch-backport kernel reboot
Fajar A. Nugraha
list at fajar.net
Tue Aug 14 09:32:03 UTC 2018
On Tue, Aug 14, 2018 at 1:54 PM, Tony Lewis <tony at lewistribe.com> wrote:
> Apologies in advance for the bump, but does anyone have an insights on
> this?
>
>
Did you install lxd before using source instead of snap?
=> lxd.service loaded active exited LSB: Container hypervisor based on
LXC
You shouldn't have that when installing lxd from snap. If yes, I suggest
cleaning out all traces of it (e.g. in /bin, /usr, /usr/local/bin) to avoid
potential confusion.
root 2452 1823 5 11:42 ? 00:00:08 lxd --logfile
>> /var/snap/lxd/common/lxd/logs/lxd.log --group lxd
>>
>
What does /var/snap/lxd/common/lxd/logs/lxd.log say? Does it have any error?
My GUESS is that you have /usr/bin/lxd and /snap/bin/lxd, which interfere
with each other. If that's not it, then my next guess is that there's
probably some group issue, like
https://github.com/lxc/lxd/issues/1861#issuecomment-206507631 . In any case
lxd.log might have more info.
Another way to make sure the issue is reproducible is if you can try
similar setup (snap-lxd + stretch backport kernel) in a fresh environment
(e.g. in a VM).
--
Fajar
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxcontainers.org/pipermail/lxc-users/attachments/20180814/33c7e142/attachment-0001.html>
More information about the lxc-users
mailing list