Repository: mesos
Updated Branches:
  refs/heads/master 3424a3d1e -> af2a707c3


Documented provisioner auto backend semantic.

Review: https://reviews.apache.org/r/56904/


Project: http://git-wip-us.apache.org/repos/asf/mesos/repo
Commit: http://git-wip-us.apache.org/repos/asf/mesos/commit/af2a707c
Tree: http://git-wip-us.apache.org/repos/asf/mesos/tree/af2a707c
Diff: http://git-wip-us.apache.org/repos/asf/mesos/diff/af2a707c

Branch: refs/heads/master
Commit: af2a707c371d2dde79680794cb22dae23f79ca7f
Parents: 3424a3d
Author: Gilbert Song <[email protected]>
Authored: Thu Feb 23 17:31:42 2017 -0800
Committer: Jie Yu <[email protected]>
Committed: Thu Feb 23 17:38:15 2017 -0800

----------------------------------------------------------------------
 docs/container-image.md | 25 +++++++++++++++++++++++--
 1 file changed, 23 insertions(+), 2 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/mesos/blob/af2a707c/docs/container-image.md
----------------------------------------------------------------------
diff --git a/docs/container-image.md b/docs/container-image.md
index 6740ce1..11e8a62 100644
--- a/docs/container-image.md
+++ b/docs/container-image.md
@@ -285,8 +285,29 @@ is `/tmp/mesos/store/appc`.
 ## Provisioner Backends
 
 A provisioner backend takes a set of filesystem layers and stacks them
-into a root filesystem. The following backends are supported
-currently.
+into a root filesystem. Currently, we support the following backends:
+copy`, `bind`, `overlay` and `aufs`. Mesos will validate if the
+selected backend works with the underlying filesystem (the filesystem
+used by the image store `--docker_store_dir` or `--appc_store_dir`)
+using the following logic table:
+
+    +---------+--------------+------------------------------------------+
+    | Backend | Suggested on | Disabled on                              |
+    +---------+--------------+------------------------------------------+
+    | aufs    | ext4 xfs     | btrfs aufs eCryptfs                      |
+    | overlay | ext4 xfs     | btrfs aufs overlay overlay2 zfs eCryptfs |
+    | bind    |              | N/A(`--sandbox_directory' must exist)    |
+    | copy    |              | N/A                                      |
+    +---------+--------------+------------------------------------------+
+
+The provisioner backend can be specified through the agent flag
+`--provisioner_image_backend`. If not set, Mesos will select the best
+backend automatically for the users/operators. The selection logic is
+as following:
+
+    1. Use `overlay` backend if the overlayfs is available.
+    2. Use `aufs` backend if the aufs is available and overlayfs is not 
supported.
+    3. Use `copy` backend if none of above is selected.
 
 ### Copy
 

Reply via email to