docker
/
docs
mirror of https://github.com/docker/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #7271 from docker/bermudezmt-patch-1 

Grammar fixes
This commit is contained in:
Anne Henmi 2018-08-28 14:23:07 -06:00 committed by GitHub
parent 0fabbd8456 ab5ad46fc2
commit 38305a68c7
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
storage/storagedriver/device-mapper-driver.md
View File

@ -19,7 +19,7 @@ Docker.
The `devicemapper` driver uses block devices dedicated to Docker and operates at
the block level, rather than the file level. These devices can be extended by
adding physical storage to your Docker host, and they perform better than using
a filesystem at the level of the operating system.
a filesystem at the operating system (OS) level.
## Prerequisites
@ -32,8 +32,8 @@ a filesystem at the level of the operating system.
- Changing the storage driver makes any containers you have already
created inaccessible on the local system. Use `docker save` to save containers,
and push existing images to Docker Hub or a private repository, so that you
not need to re-create them later.
and push existing images to Docker Hub or a private repository, so you do
not need to recreate them later.
## Configure Docker with the `devicemapper` storage driver
@ -136,14 +136,14 @@ below to configure Docker to use the `devicemapper` storage driver in
> **Warning**: Changing the storage driver makes any containers you have already
created inaccessible on the local system. Use `docker save` to save containers,
and push existing images to Docker Hub or a private repository, so that you
don't need to recreate them later.
and push existing images to Docker Hub or a private repository, so you do not
need to recreate them later.
#### Allow Docker to configure direct-lvm mode
In Docker 17.06 and higher, Docker can manage the block device for you,
simplifying configuration of `direct-lvm` mode. **This is appropriate for fresh
Docker set-ups only.** You can only use a single block device. If you need to
With Docker `17.06` and higher, Docker can manage the block device for you,
simplifying configuration of `direct-lvm` mode. **This is appropriate for fresh
Docker setups only.** You can only use a single block device. If you need to
use multiple block devices, [configure direct-lvm mode
manually](#configure-direct-lvm-mode-manually) instead. The following new
configuration options have been added:
@ -158,7 +158,7 @@ configuration options have been added:
| `dm.directlvm_device_force` | Whether to format the block device even if a filesystem already exists on it. If set to `false` and a filesystem is present, an error is logged and the filesystem is left intact. | No | false | `dm.directlvm_device_force=true` |
Edit the `daemon.json` file and set the appropriate options, then restart Docker
for the changes to take effect. The following `daemon.json` sets all of the
for the changes to take effect. The following `daemon.json` configuration sets all of the
options in the table above.
```json