> Canonical, We installed thin-provisioning-tools and have tested and not able to see the issue.
> Our tester need some clarification related to the update done above..
The summary for you and your tester for now IMHO is:
1. it is not a "bug" in docker.io
2. if thin-provisioning-tools are installed things work just fine
3. the bug was re-targeted against LVM2 to consider there if
3a. lvm should reject to create thin pools if the tools are missing
3b. lvm should have a harder dependency (component mismatch, so MIR needed)
I think for now we are waiting on feedback from lvm maintainers in Ubuntu and Debian.
> Canonical, We installed thin-provisioni ng-tools and have tested and not able to see the issue.
> Our tester need some clarification related to the update done above..
The summary for you and your tester for now IMHO is: ng-tools are installed things work just fine
1. it is not a "bug" in docker.io
2. if thin-provisioni
3. the bug was re-targeted against LVM2 to consider there if
3a. lvm should reject to create thin pools if the tools are missing
3b. lvm should have a harder dependency (component mismatch, so MIR needed)
I think for now we are waiting on feedback from lvm maintainers in Ubuntu and Debian.