Re: [lxc-users] Containers won't start under stretch-backport kernel reboot

On Wed, Aug 15, 2018 at 9:52 AM, Tony Lewis wrote: > Aug 15 11:40:50 server snap[6761]: lxd: error while loading shared > libraries: liblxc.so.1: cannot open shared object file: No such file or > directory > This is something to follow up The library is present in what looks to be the right

Re: [lxc-users] Containers won't start under stretch-backport kernel reboot

Thank you Fajar. I have made some progress, but would still value help (fresh detail at the bottom). On 14/08/18 19:32, Fajar A. Nugraha wrote: On Tue, Aug 14, 2018 at 1:54 PM, Tony Lewis > wrote: Apologies in advance for the bump, but does anyone have an

Re: [lxc-users] Containers won't start under stretch-backport kernel reboot

On Tue, Aug 14, 2018 at 1:54 PM, Tony Lewis 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 exitedLSB: Container hypervisor based on LXC You shouldn't have that

Re: [lxc-users] Containers won't start under stretch-backport kernel reboot

Apologies in advance for the bump, but does anyone have an insights on this? On 11/08/18 16:23, Tony Lewis wrote: I have been running LXD/LXC on a stock Debian Stretch kernel(4.9.0-7-amd64), and it's working fine.  But it's beneficial for me to go to the Stretch Backports

[lxc-users] Containers won't start under stretch-backport kernel reboot

I have been running LXD/LXC on a stock Debian Stretch kernel(4.9.0-7-amd64), and it's working fine.  But it's beneficial for me to go to the Stretch Backports (4.17.0-0.bpo.1-amd64). When I do, my container's won't start until I forcefully kill the LXD daemon and restart the service. Details