WIP: Consistent device usage in devicemapper examples #3032
Conversation
The existing docs use inconsistent names for the docker volume, and the thinpool logical volume names. I've updated the docs to use `docker` consistently as the volume group name, and `docker/thinpool` as the logical volume in all examples. this makes the docs easier to comprehend, since users don't have to go through multiple times to realize the names of volumes keep switching halfway through the example.
It seems latest versions of docker don't want the fully qualified device path in the `dm.thinpooldev` setting. Systemd fails to start docker daemon if I use `/dev/vgname/lvname` _or_ `/dev/mapper/vgname-lvname`. When using devicemapper, all it wants is the name of the thinpool.
With no containers running, the output of `lsblk` will only show the thin lvm devices, and not the dm thin volumes.
LongLiveCHIEF
changed the title
|
How is this coming along? |
|
This is still listed as WIP and has a merge conflict. Any update? |
|
There was a recent update to projectatomic/container-storage-setup, and I've been working through issues in consistency between manual setup using the current docs, running the latest css, and some issues with selinux enabled hosts. It's already been a long week with this one, but I hope to be able to take definitive action on this PR by the end of the week. |
|
The issue mentioned in css: passing -n ftype=1 hits the nail on the head with the selinux issues. Especially running |
|
After reviewing the changes, I don't think there's any point in rebasing. I think the upstream changes covered everything I was going to do with this PR. |
Proposed changes
The existing docs use inconsistent names for the docker volume, and the thinpool logical volume names. I've updated the docs to use
dockerconsistently as the volume group name, anddocker/thinpoolas the logical volume in all examples.this makes the docs easier to comprehend, since users don't have to go through multiple times to realize the names of volumes keep switching halfway through the example.