This is an automated email from the ASF dual-hosted git repository.

git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/mesos-site.git


The following commit(s) were added to refs/heads/asf-site by this push:
     new 3c5d778  Updated the website built from mesos SHA: c705345.
3c5d778 is described below

commit 3c5d77864d411744474a5c186e8a09176a689439
Author: jenkins <[email protected]>
AuthorDate: Tue Aug 21 22:33:58 2018 +0000

    Updated the website built from mesos SHA: c705345.
---
 content/documentation/container-image/index.html            | 5 ++++-
 content/documentation/latest/configuration/agent/index.html | 6 +++---
 content/documentation/latest/container-image/index.html     | 5 ++++-
 3 files changed, 11 insertions(+), 5 deletions(-)

diff --git a/content/documentation/container-image/index.html 
b/content/documentation/container-image/index.html
index a03def7..7729b58 100644
--- a/content/documentation/container-image/index.html
+++ b/content/documentation/container-image/index.html
@@ -336,7 +336,10 @@ example, the operator can put a 
<code>busybox:latest.tar</code> (the result of
 <code>/tmp/mesos/images/docker</code> and launch the agent by specifying
 <code>--docker_registry=/tmp/mesos/images/docker</code>. Then the framework can
 launch a Docker container by specifying <code>busybox:latest</code> as the name
-of the Docker image.</p>
+of the Docker image. This flag can also point to an HDFS URI
+(<em>experimental</em> in Mesos 1.7) (e.g., 
<code>hdfs://localhost:8020/archives/</code>)
+to fetch images from HDFS if the <code>hadoop</code> command is available on 
the
+agent.</p>
 
 <p>If the <code>--switch_user</code> flag is set on the agent and the framework
 specifies a user (either <code>CommandInfo.user</code> or 
<code>FrameworkInfo.user</code>),
diff --git a/content/documentation/latest/configuration/agent/index.html 
b/content/documentation/latest/configuration/agent/index.html
index 3cc551d..0a6e7c1 100644
--- a/content/documentation/latest/configuration/agent/index.html
+++ b/content/documentation/latest/configuration/agent/index.html
@@ -757,11 +757,11 @@ recovers.
   </td>
   <td>
 The default url for Mesos containerizer to pull Docker images. It could
-either be a Docker registry server url (i.e: 
<code>https://registry.docker.io</code>),
+either be a Docker registry server url (e.g., 
<code>https://registry.docker.io</code>),
 or a source that Docker image archives (result of <code>docker save</code>) are
 stored. The Docker archive source could be specified either as a local
-path (i.e: <code>/tmp/docker/images</code>), or as an HDFS URI
-(i.e: <code>hdfs://localhost:8020/archives/</code>). Note that this option 
won't
+path (e.g., <code>/tmp/docker/images</code>), or as an HDFS URI 
(*experimental*)
+(e.g., <code>hdfs://localhost:8020/archives/</code>). Note that this option 
won't
 change the default registry server for Docker containerizer.
 (default: https://registry-1.docker.io)
   </td>
diff --git a/content/documentation/latest/container-image/index.html 
b/content/documentation/latest/container-image/index.html
index 5814418..b92d782 100644
--- a/content/documentation/latest/container-image/index.html
+++ b/content/documentation/latest/container-image/index.html
@@ -336,7 +336,10 @@ example, the operator can put a 
<code>busybox:latest.tar</code> (the result of
 <code>/tmp/mesos/images/docker</code> and launch the agent by specifying
 <code>--docker_registry=/tmp/mesos/images/docker</code>. Then the framework can
 launch a Docker container by specifying <code>busybox:latest</code> as the name
-of the Docker image.</p>
+of the Docker image. This flag can also point to an HDFS URI
+(<em>experimental</em> in Mesos 1.7) (e.g., 
<code>hdfs://localhost:8020/archives/</code>)
+to fetch images from HDFS if the <code>hadoop</code> command is available on 
the
+agent.</p>
 
 <p>If the <code>--switch_user</code> flag is set on the agent and the framework
 specifies a user (either <code>CommandInfo.user</code> or 
<code>FrameworkInfo.user</code>),

Reply via email to