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

Remove misleading generic storage driver instructions (#5619)

This commit is contained in:
Misty Stanley-Jones 2017-12-26 12:27:26 -08:00 committed by GitHub
parent 73c8ff17a9
commit cd1260a28d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 11 additions and 35 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

46
engine/userguide/storagedriver/selectadriver.md
View File

@ -200,15 +200,10 @@ storage drivers. Make sure to use equivalent hardware and workloads to match
production conditions, so you can see which storage driver offers the best production conditions, so you can see which storage driver offers the best
overall performance. overall performance.
## Check and set your current storage driver ## Check your current storage driver
The detailed documentation for each individual storage driver details all of the The detailed documentation for each individual storage driver details all of the
set-up steps to use a given storage driver. This is a very high-level summary of set-up steps to use a given storage driver.
how to change the storage driver.
> **Important**: Some storage driver types, such as `devicemapper`, `btrfs`, and
> `zfs`, require additional set-up at the operating system level before you can
> use them with Docker.
To see what storage driver Docker is currently using, use `docker info` and look To see what storage driver Docker is currently using, use `docker info` and look
for the `Storage Driver` line: for the `Storage Driver` line:
@ -223,35 +218,16 @@ Storage Driver: overlay
<output truncated> <output truncated>
``` ```
To change the storage driver, see the specific instructions for the new storage
driver. Some drivers require additional configuration, including configuration
to physical or logical disks on the Docker host.
> **Important**: When you change the storage driver, any existing images and
To set the storage driver, you can use the `--storage-driver` flag when starting > containers become inaccessible. This is because their layers cannot be used
the Docker daemon manually, or (recommended) set the option in the `daemon.json` > by the new storage driver. If you revert your changes, you will be able to
file, which is located in `/etc/docker/` on Linux and > access the old images and containers again, but any that you pulled or
`C:\ProgramData\docker\config\` on Windows Server. > created using the new driver will then be inaccessible.
{:.important}
> **Note**: Using the `--storage-driver` flag when running `dockerd` manually or
> using an init script is not recommended. We recommend setting the option in
> the `daemon.json` file instead, because this mechanism is cross-platform,
> and will not create configuration conflicts with the default init scripts for
> your operating system.
Changing the storage driver on Docker for Mac or Docker for Windows is not
supported.
If the `daemon.json` file does not exist, create it. Assuming there are no other
settings in the file, it should have the following contents:
```json
{
"storage-driver": "devicemapper"
}
```
You can specify any valid storage driver in place of `devicemapper`.
Restart Docker for the changes to take effect. After restarting, run
`docker info` again to verify that the new storage driver is being used.
## Related information ## Related information