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

docs: update graphdriver compatibility matrix 

Signed-off-by: Sven Dowideit <SvenDowideit@home.org.au>
This commit is contained in:
Sven Dowideit 2016-05-12 08:06:41 +10:00
parent 60abc96acf
commit a7bf4e4832
1 changed files with 11 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
docs/userguide/storagedriver/selectadriver.md
View File

@ -40,10 +40,10 @@ driver names:
|AUFS |`aufs` | |AUFS |`aufs` |
|Btrfs |`btrfs` | |Btrfs |`btrfs` |
|Device Mapper |`devicemapper` | |Device Mapper |`devicemapper` |
|VFS* |`vfs` | |VFS |`vfs` |
|ZFS |`zfs` | |ZFS |`zfs` |
To find out which storage driver is set on the daemon , you use the To find out which storage driver is set on the daemon, you use the
`docker info` command: `docker info` command:
$ docker info $ docker info
@ -71,18 +71,18 @@ For example, the `btrfs` storage driver on a Btrfs backing filesystem. The
following table lists each storage driver and whether it must match the host's following table lists each storage driver and whether it must match the host's
backing file system: backing file system:
|Storage driver |Must match backing filesystem |Incompatible with | |Storage driver |Commonly used on |Disabled on |
|---------------|------------------------------|--------------------| |---------------|-----------------|------------------------------|
|`overlay` |No |`btrfs` `aufs` `zfs`| |`overlay` |`ext4` `xfs` |`btrfs` `aufs` `overlay` `zfs`|
|`aufs` |No |`btrfs` `aufs` | |`aufs` |`ext4` `xfs` |`btrfs` `aufs` |
|`btrfs` |Yes | N/A | |`btrfs` |`btrfs` _only_ | N/A |
|`devicemapper` |No | N/A | |`devicemapper` |`direct-lvm` | N/A |
|`vfs` |No | N/A | |`vfs` |debugging only | N/A |
|`zfs` |Yes | N/A | |`zfs` |`zfs` _only_ | N/A |
> **Note** > **Note**
> Incompatible with means some storage drivers can not run over certain backing > "Disabled on" means some storage drivers can not run over certain backing
> filesystem. > filesystem.
You can set the storage driver by passing the `--storage-driver=<name>` option You can set the storage driver by passing the `--storage-driver=<name>` option