overlayfs: more helpful output when not supported
| ... | ... |
@@ -129,6 +129,7 @@ func supportsOverlayfs() error {
|
| 129 | 129 |
return nil |
| 130 | 130 |
} |
| 131 | 131 |
} |
| 132 |
+ log.Error("'overlayfs' not found as a supported filesystem on this host. Please ensure kernel is new enough and has overlayfs support loaded.")
|
|
| 132 | 133 |
return graphdriver.ErrNotSupported |
| 133 | 134 |
} |
| 134 | 135 |
|
| ... | ... |
@@ -156,7 +156,7 @@ string is equivalent to setting the `--tlsverify` flag. The following are equiva |
| 156 | 156 |
### Daemon storage-driver option |
| 157 | 157 |
|
| 158 | 158 |
The Docker daemon has support for three different image layer storage drivers: `aufs`, |
| 159 |
-`devicemapper`, and `btrfs`. |
|
| 159 |
+`devicemapper`, `btrfs` and `overlayfs`. |
|
| 160 | 160 |
|
| 161 | 161 |
The `aufs` driver is the oldest, but is based on a Linux kernel patch-set that |
| 162 | 162 |
is unlikely to be merged into the main kernel. These are also known to cause some |
| ... | ... |
@@ -175,6 +175,9 @@ To tell the Docker daemon to use `devicemapper`, use |
| 175 | 175 |
The `btrfs` driver is very fast for `docker build` - but like `devicemapper` does not |
| 176 | 176 |
share executable memory between devices. Use `docker -d -s btrfs -g /mnt/btrfs_partition`. |
| 177 | 177 |
|
| 178 |
+The `overlayfs` is a very fast union filesystem. It is now merged in the main |
|
| 179 |
+Linux kernel as of [3.18.0](https://lkml.org/lkml/2014/10/26/137). |
|
| 180 |
+Call `docker -d -s overlayfs` to use it. |
|
| 178 | 181 |
|
| 179 | 182 |
### Docker exec-driver option |
| 180 | 183 |
|