man pages for both "docker" and "docker-storage-setup": From "man docker-storage-setup", the note on STORAGE_DRIVER claims that the possible storage driver values are "devicemapper", "overlay" or "", which appears correct (are there any others? What about AUFS?) However, the man page for "docker", in the section "EXEC DRIVER OPTIONS", reads: "Use the --exec-opt flags to specify options to the exec-driver. The only driver that accepts this flag is the native (libcontainer) driver. As a result, you must also specify -s=native ..." ^^^^^^^^^ But as "-s" is the option to select a storage driver, "native" doesn't appear to be a valid choice. Perhaps the author above meant "-e=native"? As for the rest of "man docker-storage-setup": CHUNK_SIZE: Controls the chunk size/block size of thin pool. Value of CHUNK_SIZE [must?] be suitable ... ^^^^^ "well as some values acceptable to to "lvcreate -l". If user" ^^ Finally, there is the line: "The options below should be specified as values acceptable to 'lvextend -L': but the entire discussion of DATA_SIZE is in terms of "lvcreate", not "lvextend", which might be deliberate, I just thought I'd mention it. That should do it.
Upon further examination, aren't there other possible storage driver options? vfs? btrfs? The man page doesn't mention those.
Vivek any update
Sally can you get this fixed in the next few days?
PR Opened upstream. https://github.com/projectatomic/docker-storage-setup/pull/100 https://github.com/docker/docker/pull/19165 Shishir
PR's merged upstream. Shishir
Nice