[ARVADOS] updated: 2.1.0-1165-gb74bc9107

[Git user]

Summary of changes:
 doc/install/singularity.html.textile.liquid | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

       via  b74bc91079b0c2b5491e08f8ff677451c6d7e60e (commit)
      from  d069271ec828654f9a6b656b04b40f229cfefb27 (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 b74bc91079b0c2b5491e08f8ff677451c6d7e60e
Author: Tom Clegg <tom at curii.com>
Date:   Mon Aug 9 09:49:03 2021 -0400

    17726: More detail about singularity/docker differences.
    
    Arvados-DCO-1.1-Signed-off-by: Tom Clegg <tom at curii.com>

diff --git a/doc/install/singularity.html.textile.liquid b/doc/install/singularity.html.textile.liquid
index b3cbe593b..121dd86c6 100644
--- a/doc/install/singularity.html.textile.liquid
+++ b/doc/install/singularity.html.textile.liquid
@@ -9,13 +9,15 @@ Copyright (C) The Arvados Authors. All rights reserved.
 SPDX-License-Identifier: CC-BY-SA-3.0
 {% endcomment %}
 
-Arvados can be configured to use Singularity instead of Docker to execute containers on cloud nodes or a SLURM/LSF cluster.
+Arvados can be configured to use "Singularity":https://sylabs.io/singularity/ instead of Docker to execute containers on cloud nodes or a SLURM/LSF cluster.
 
 Please note:
 * *Singularity support is currently considered experimental.*
 * Even when using the singularity runtime, users' container images are expected to be saved in Docker format using @arv keep docker at . Arvados converts the Docker image to Singularity format (@.sif@) at runtime as needed. Specifying a @.sif@ file as an image when submitting a container request is not yet supported.
-* Singularity does not limit the amount of memory available in a container. Each container will have access to all memory on the host where it runs.
-* Programs running in containers may behave differently due to differences between Singularity and Docker, _e.g._, the root (image) filesystem is read-only in a Singularity container.
+* Singularity does not limit the amount of memory available in a container. Each container will have access to all memory on the host where it runs, unless memory use is restricted by SLURM/LSF.
+* Programs running in containers may behave differently due to differences between Singularity and Docker.
+** The root (image) filesystem is read-only in a Singularity container. Programs that attempt to write outside a designated output or temporary directory are likely to fail.
+** The Docker ENTRYPOINT instruction is ignored.
 * Arvados is currently tested with Singularity version 3.5.2.
 
 To use singularity, first make sure "Singularity is installed":https://sylabs.io/guides/3.5/user-guide/quick_start.html on your cloud worker image or SLURM/LSF compute nodes as applicable. Note @squashfs-tools@ is required.

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


hooks/post-receive
--