1berry/docker-cli
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

daemon option (--storage-opt dm.basesize) for increasing the base device size on daemon restart

Browse Source 
Signed-off-by: Shishir Mahajan <shishir.mahajan@redhat.com>
This commit is contained in:
Shishir Mahajan 2016-01-12 13:44:13 -05:00 committed by Tibor Vass
parent 7f6a7ed8d1
commit 1e83a27ca1
2 changed files with 28 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
docs/reference/commandline/daemon.md
View File

@ -213,11 +213,23 @@ options for `zfs` start with `zfs`.
* `dm.basesize` * `dm.basesize`
Specifies the size to use when creating the base device, which limits the Specifies the size to use when creating the base device, which limits the
size of images and containers. The default value is 100G. Note, thin devices size of images and containers. The default value is 10G. Note, thin devices
are inherently "sparse", so a 100G device which is mostly empty doesn't use are inherently "sparse", so a 10G device which is mostly empty doesn't use
100 GB of space on the pool. However, the filesystem will use more space for 10 GB of space on the pool. However, the filesystem will use more space for
the empty case the larger the device is. the empty case the larger the device is.
The base device size can be increased at daemon restart which will allow
all future images and containers (based on those new images) to be of the
new base device size.
Example use:
$ docker daemon --storage-opt dm.basesize=50G
This will increase the base device size to 50G. The Docker daemon will throw an
error if existing base device size is larger than 50G. A user can use
this option to expand the base device size however shrinking is not permitted.
This value affects the system-wide "base" empty filesystem This value affects the system-wide "base" empty filesystem
that may already be initialized and inherited by pulled images. Typically, that may already be initialized and inherited by pulled images. Typically,
a change to this value requires additional steps to take effect: a change to this value requires additional steps to take effect:

16
man/docker-daemon.8.md
View File

@ -271,12 +271,22 @@ Example use: `docker daemon --storage-opt dm.thinpooldev=/dev/mapper/thin-pool`
#### dm.basesize #### dm.basesize
Specifies the size to use when creating the base device, which limits Specifies the size to use when creating the base device, which limits
the size of images and containers. The default value is 100G. Note, the size of images and containers. The default value is 10G. Note,
thin devices are inherently "sparse", so a 100G device which is mostly thin devices are inherently "sparse", so a 10G device which is mostly
empty doesn't use 100 GB of space on the pool. However, the filesystem empty doesn't use 10 GB of space on the pool. However, the filesystem
will use more space for base images the larger the device will use more space for base images the larger the device
is. is.
The base device size can be increased at daemon restart which will allow
all future images and containers (based on those new images) to be of the
new base device size.
Example use: `docker daemon --storage-opt dm.basesize=50G`
This will increase the base device size to 50G. The Docker daemon will throw an
error if existing base device size is larger than 50G. A user can use
this option to expand the base device size however shrinking is not permitted.
This value affects the system-wide "base" empty filesystem that may already This value affects the system-wide "base" empty filesystem that may already
be initialized and inherited by pulled images. Typically, a change to this be initialized and inherited by pulled images. Typically, a change to this
value requires additional steps to take effect: value requires additional steps to take effect: