19095: Remove bit about loopback device errors in singularity 3.9.1.

Arvados-DCO-1.1-Signed-off-by: Tom Clegg <tom@curii.com>

diff --git a/doc/install/crunch2/install-compute-node-singularity.html.textile.liquid b/doc/install/crunch2/install-compute-node-singularity.html.textile.liquid
index cb0e3c3a4c02d7f31554186c3acadd23ea20ce95..10c18d733f06a533f6cca15bc67972e25855a7a8 100644 (file)
--- a/doc/install/crunch2/install-compute-node-singularity.html.textile.liquid
+++ b/doc/install/crunch2/install-compute-node-singularity.html.textile.liquid
@@ -56,20 +56,3 @@ Then update @Containers.RuntimeEngine@ in your cluster configuration:
 </notextile>
 
 {% include 'singularity_mksquashfs_configuration' %}
-
-h2(#singularity_loop_device_errors). Singularity loop device errors
-
-With singularity v3.9.1 and earlier, containers may fail intermittently at startup with an error message similar to the following in the container log's @stderr.txt@ (line breaks added):
-
-<notextile>
-<pre><code>FATAL:   container creation failed:
- mount /proc/self/fd/3->/usr/local/var/singularity/mnt/session/rootfs error:
- while mounting image /proc/self/fd/3:
- failed to find loop device:
- could not attach image file to loop device:
- failed to set loop flags on loop device:
- resource temporarily unavailable
-</code></pre>
-</notextile>
-
-This problem is addressed in singularity v3.9.2. For details, please see "Arvados issue #18489":https://dev.arvados.org/issues/18489 and "singularity PR #458":https://github.com/sylabs/singularity/pull/458.