[ARVADOS] updated: ee4b429bc5680c8aa846bb4320629e370f2a146e

Git user git at public.curoverse.com
Wed Mar 22 12:56:39 EDT 2017


Summary of changes:
 .../crunch2-slurm/install-dispatch.html.textile.liquid    | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

       via  ee4b429bc5680c8aa846bb4320629e370f2a146e (commit)
      from  6ec5886c0f758745a2205b0d94e6e83efcff0d48 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.


commit ee4b429bc5680c8aa846bb4320629e370f2a146e
Author: Peter Amstutz <peter.amstutz at curoverse.com>
Date:   Wed Mar 22 12:56:34 2017 -0400

    11255: Add documentation about configuration to enable host networking always.

diff --git a/doc/install/crunch2-slurm/install-dispatch.html.textile.liquid b/doc/install/crunch2-slurm/install-dispatch.html.textile.liquid
index e6b8e1e..f50534e 100644
--- a/doc/install/crunch2-slurm/install-dispatch.html.textile.liquid
+++ b/doc/install/crunch2-slurm/install-dispatch.html.textile.liquid
@@ -120,6 +120,21 @@ You can work around this issue by disabling the Docker daemon's systemd integrat
 
 {% include 'notebox_end' %}
 
+h3. CrunchRunCommand: Using host networking for containers
+
+Older Linux kernels (prior to 3.18) have bugs in network namespace handling which can lead to compute node lockups.  This by is indicated by blocked kernel tasks in "Workqueue: netns cleanup_net".   If you are experiencing this problem, as a workaround you can disable use of network namespaces by Docker across the cluster.  Be aware this reduces container isolation, which may be a security risk.
+
+<notextile>
+<pre><code class="userinput">Client:
+  APIHost: <b>zzzzz.arvadosapi.com</b>
+  AuthToken: <b>zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz</b>
+CrunchRunCommand:
+- <b>crunch-run</b>
+- <b>"-container-enable-networking=always"</b>
+- <b>"-container-network-mode=host"</b>
+</code></pre>
+</notextile>
+
 h3. MinRetryPeriod: Rate-limit repeated attempts to start containers
 
 If SLURM is unable to run a container, the dispatcher will submit it again after the next PollPeriod. If PollPeriod is very short, this can be excessive. If MinRetryPeriod is set, the dispatcher will avoid submitting the same container to SLURM more than once in the given time span.

-----------------------------------------------------------------------


hooks/post-receive
-- 




More information about the arvados-commits mailing list