Bug 1249652 - Some notes on "man docker-storage-setup".
Summary: Some notes on "man docker-storage-setup".
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: docker
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
Assignee: smahajan@redhat.com
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-03 13:45 UTC by Robert P. J. Day
Modified: 2016-02-16 20:02 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-16 20:02:41 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Robert P. J. Day 2015-08-03 13:45:06 UTC
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.

Comment 1 Robert P. J. Day 2015-08-08 10:57:16 UTC
Upon further examination, aren't there other possible storage driver options? vfs? btrfs? The man page doesn't mention those.

Comment 2 Daniel Walsh 2015-09-28 18:59:56 UTC
Vivek any update

Comment 3 Daniel Walsh 2015-12-01 21:52:33 UTC
Sally can you get this fixed in the next few days?

Comment 5 smahajan@redhat.com 2016-01-07 16:23:24 UTC
PR Opened upstream.

https://github.com/projectatomic/docker-storage-setup/pull/100
https://github.com/docker/docker/pull/19165

Shishir

Comment 6 smahajan@redhat.com 2016-01-08 16:10:43 UTC
PR's merged upstream.

Shishir

Comment 7 Daniel Walsh 2016-01-08 18:23:19 UTC
Nice


Note You need to log in before you can comment on or make changes to this bug.