Browse code
docs: update graphdriver compatibility matrix
Signed-off-by: Sven Dowideit <SvenDowideit@home.org.au>
Sven Dowideit authored on 2016/05/12 07:06:41Showing 1 changed files
| ... | ... |
@@ -40,10 +40,10 @@ driver names: |
| 40 | 40 |
|AUFS |`aufs` | |
| 41 | 41 |
|Btrfs |`btrfs` | |
| 42 | 42 |
|Device Mapper |`devicemapper` | |
| 43 |
-|VFS* |`vfs` | |
|
| 43 |
+|VFS |`vfs` | |
|
| 44 | 44 |
|ZFS |`zfs` | |
| 45 | 45 |
|
| 46 |
-To find out which storage driver is set on the daemon , you use the |
|
| 46 |
+To find out which storage driver is set on the daemon, you use the |
|
| 47 | 47 |
`docker info` command: |
| 48 | 48 |
|
| 49 | 49 |
$ docker info |
| ... | ... |
@@ -71,18 +71,18 @@ For example, the `btrfs` storage driver on a Btrfs backing filesystem. The |
| 71 | 71 |
following table lists each storage driver and whether it must match the host's |
| 72 | 72 |
backing file system: |
| 73 | 73 |
|
| 74 |
-|Storage driver |Must match backing filesystem |Incompatible with | |
|
| 75 |
-|---------------|------------------------------|--------------------| |
|
| 76 |
-|`overlay` |No |`btrfs` `aufs` `zfs`| |
|
| 77 |
-|`aufs` |No |`btrfs` `aufs` | |
|
| 78 |
-|`btrfs` |Yes | N/A | |
|
| 79 |
-|`devicemapper` |No | N/A | |
|
| 80 |
-|`vfs` |No | N/A | |
|
| 81 |
-|`zfs` |Yes | N/A | |
|
| 74 |
+|Storage driver |Commonly used on |Disabled on | |
|
| 75 |
+|---------------|-----------------|------------------------------| |
|
| 76 |
+|`overlay` |`ext4` `xfs` |`btrfs` `aufs` `overlay` `zfs`| |
|
| 77 |
+|`aufs` |`ext4` `xfs` |`btrfs` `aufs` | |
|
| 78 |
+|`btrfs` |`btrfs` _only_ | N/A | |
|
| 79 |
+|`devicemapper` |`direct-lvm` | N/A | |
|
| 80 |
+|`vfs` |debugging only | N/A | |
|
| 81 |
+|`zfs` |`zfs` _only_ | N/A | |
|
| 82 | 82 |
|
| 83 | 83 |
|
| 84 | 84 |
> **Note** |
| 85 |
-> Incompatible with means some storage drivers can not run over certain backing |
|
| 85 |
+> "Disabled on" means some storage drivers can not run over certain backing |
|
| 86 | 86 |
> filesystem. |
| 87 | 87 |
|
| 88 | 88 |
You can set the storage driver by passing the `--storage-driver=<name>` option |