The docs and time saving

The storage type lvm is not named correctly
because it implies attaching to an lv
whereas lxd wants to consume a vg
so the name of the storage should be vg not lvm
nowhere obvious in the docs does it lead me to the correct conclusion
in-fact I would say the docs actually cause you more man power to support with new tickets/issues
your docs are kind of like a cook book that just describes the smell of the food and the idea of the recipe
if you add some bash examples in a lot of places in the docs then they will be much more usable
and you will have far less confused users and time spent on answering questions
much love

user #feedback

think cookbook

If you had a cook book that had no instructions but has a set amount of musings, ideas, recommendations. would you buy this book to learn to cook the recipes?

(I have never seen such a cook book)

would you buy it or use it vs one that has some example applications on each recipe?

#Hint: all cookbooks have instructions for every recipe.

it makes sense, do you want to be popular or not?

do you want to be always answering questions or not?

it would be far better to use the best answers to fill in gaps in the docs with multiple example bash snippets

harvest solved answers into examples in the docs

do it actively!
= less support needed

you can hire 1 or 2 persons to solely make sure that this kind of action is maintained
not difficult
or you want to be not as used as docker?
i’d rather LXD be the norm.

The docs on the LVM driver are here:

There’s a fair amount of description of the underlying terminology used by the upstream project (LVM is not a subproject of LXD and we didn’t make the name :)).


LVM can combine several physical storage devices into a volume group.


The lvm driver in LXD uses logical volumes for images, and volume snapshots for instances and snapshots.

LXD assumes that it has full control over the volume group. Therefore, you should not maintain any file system entities that are not owned by LXD in an LVM volume group, because LXD might delete them.

In the configuration section the source setting is defined as:

Path to an existing block device, loop file or LVM volume group

In the “Manage pools” section there are various examples of setting up pools, including LVM ones:

Including an example of using an existing volume group:

Use the existing LVM volume group called my-pool for pool2:
lxc storage create pool2 lvm source=my-pool

We do have a member of the team who is focused on documentation and has been improving the documentation and adding how tos. But I’m sure you can agree that we cannot add how tos for every specific custom setup.

We do also have the Tutorials section of the forum here Tutorials - Linux Containers Forum, so if you feel that you are able to contribute something then please do write a post and we can move it to the Tutorials section for others to benefit from in the future.

Also if you feel that certain pages of the documentation can be improved then we welcome pull requests (or issues with specific suggestions) over at

1 Like

trust me
hire some people who think normal but understand (you)
and lots of normal people will be able to instantly get LXD

I’ve tried to help you on the other thread LVM - Device excluded by a filter after wipefs --all --force

I hope it helps and that you’d be willing to contribute a how to post covering it.

1 Like

i’ll get it done! #willDo
and you’d need to vet what I say then add it to official docs
(i don’t need any mention, i just would like to see the docs easy for all people)
awesome work @tomp


Lots of great ideas!

In my 20yr career at cisco systems we used to have a saying:

Nothings impossible for those that don’t do the work!

You do know that you can contribute to the Documentation yourself… right?

Maybe if you start… others will realize they can help too.


I made a tutorial @bmullan

1 Like

If you have time you might post that on the sub-reddit /r/LXD also

done, with link to source:

1 Like