Hi, I think the root of this problem is the difference in $PATH between root and a normal user -- root includes /usr/sbin/, which is where the `thin_check` binary is installed. LXD attempts to find it in the current $PATH when deciding whether or not to enable LVM thin provisioning [1].
If you include /usr/sbin/ in your $PATH, can you successfully run `lxd init`? > $ PATH=$PATH:/usr/sbin lxd init I don't have LVM setup on my test machine at the moment, but the LXD init process appeared was successful (except for actually creating the storage pool in LVM) when I replicated this bug. I suspect this will have to be forwarded upstream, but would appreciate hearing from you if this fixes the problem you've experienced. Mathias [1] -- https://github.com/lxc/lxd/blob/master/lxd/main_init_interactive.go#L913
signature.asc
Description: This is a digitally signed message part
