You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mesos.apache.org by ji...@apache.org on 2017/09/19 18:30:38 UTC
mesos git commit: Added index in the container volume doc.
Repository: mesos
Updated Branches:
refs/heads/master bcf87ad77 -> 87a3ce946
Added index in the container volume doc.
Project: http://git-wip-us.apache.org/repos/asf/mesos/repo
Commit: http://git-wip-us.apache.org/repos/asf/mesos/commit/87a3ce94
Tree: http://git-wip-us.apache.org/repos/asf/mesos/tree/87a3ce94
Diff: http://git-wip-us.apache.org/repos/asf/mesos/diff/87a3ce94
Branch: refs/heads/master
Commit: 87a3ce946a2629e3488a80414e27adbba2217e93
Parents: bcf87ad
Author: Jie Yu <yu...@gmail.com>
Authored: Tue Sep 19 11:30:34 2017 -0700
Committer: Jie Yu <yu...@gmail.com>
Committed: Tue Sep 19 11:30:34 2017 -0700
----------------------------------------------------------------------
docs/container-volume.md | 19 +++++++++++++------
1 file changed, 13 insertions(+), 6 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/mesos/blob/87a3ce94/docs/container-volume.md
----------------------------------------------------------------------
diff --git a/docs/container-volume.md b/docs/container-volume.md
index 535a61d..359d4b2 100644
--- a/docs/container-volume.md
+++ b/docs/container-volume.md
@@ -17,7 +17,14 @@ the following fields must be specified:
- `source`: Describe where the volume originates from. See more
details in the following section.
-## `HOST_PATH` Volume Source
+## Volume Source Types
+
+- [HOST\_PATH](#host_path-volume-source)
+- [SANDBOX\_PATH](#sandbox_path-volume-source)
+- [DOCKER\_VOLUME](#docker_volume-volume-source)
+- [SECRET](#secret-volume-source)
+
+### HOST\_PATH Volume Source
This volume source represents a path on the host filesystem. The path
can either point to a directory or a file (either a regular file or a
@@ -52,7 +59,7 @@ flag when starting the agent. This isolator depends on
[Docker Containerizer](docker-containerizer.md) supports `HOST_PATH`
volume as well.
-## `SANDBOX_PATH` Volume Source
+### SANDBOX\_PATH Volume Source
There are currently two types of `SANDBOX_PATH` volume sources:
[`SELF`](#self-type) and [`PARENT`](#parent-type).
@@ -65,7 +72,7 @@ the `--isolation` flag when starting the agent.
The [Docker Containerizer](docker-containerizer.md) only supports
`SELF` type `SANDBOX_PATH` volumes currently.
-### `SELF` Type
+#### `SELF` Type
This represents a path in the container's own sandbox. The path can
point to either a directory or a file in the sandbox of the container.
@@ -99,7 +106,7 @@ subdirectory in the container sandbox to another subdirectory in the
container sandbox. In that case, the user can just create a symlink,
instead of using a volume.
-### `PARENT` Type
+#### PARENT Type
This represents a path in the sandbox of the parent container. The
path can point to either a directory or a file in the sandbox of the
@@ -129,10 +136,10 @@ sandbox of the container.
The ownership of the volume will be the same as that of the sandbox of
the parent container.
-## `DOCKER_VOLUME` Volume Source
+### DOCKER\_VOLUME Volume Source
See more details in this [doc](isolators/docker-volume.md).
-## `SECRET` Volume Source
+### SECRET Volume Source
See more details in this [doc](secrets.md#file-based-secrets).