On Tue, Mar 1, 2016 at 5:55 PM, Daniel J Walsh <dwa...@redhat.com> wrote: > > > On 03/01/16 11:32, Tobias Florek wrote:
… >> Also I couldn't find a way to use a _separate_ lvm within the container >> (to manage the container's own storage). I figured, that's not possible, >> given that lvm is running mostly in the kernel. Using system-lvm from >> the container works, but wreaks havoc when using systemd units (as one >> could imagine). It unmounts most host's filesystems when shutting down >> for instance. Are there any best practices regarding it? … > Can you just do lvm commands like this > > chroot /host lvm ... I am not sure if chroot is enough, but at least you will need to run lvm in the host's context, because lvm also relies on some user-space locking which is borked if you run lvm inside a container. All in all I hope that storaged will be available on the host one day, and LVm operations can be performed through a dbus api. - fabian
