Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.dist > #1130996
| From | Mathias Gibbens <gibmat@debian.org> |
|---|---|
| Newsgroups | linux.debian.bugs.dist |
| Subject | Bug#1027321: lxd init run as non-root fails to find LVM thin provisioning tools |
| Date | 2023-01-01 00:20 +0100 |
| Message-ID | <FITiV-eH0w-1@gated-at.bofh.it> (permalink) |
| References | <FIlqV-ejxf-1@gated-at.bofh.it> <FIlqV-ejxf-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
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
Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Bug#1027321: lxd init run as non-root fails to find LVM thin provisioning tools Michael reports bugs <bugs@deegan.id.au> - 2022-12-30 12:10 +0100
Bug#1027321: lxd init run as non-root fails to find LVM thin provisioning tools Mathias Gibbens <gibmat@debian.org> - 2023-01-01 00:20 +0100
Bug#1027321: lxd init run as non-root fails to find LVM thin provisioning tools Mathias Gibbens <gibmat@debian.org> - 2023-02-26 18:40 +0100
csiph-web