X-Git-Url: https://git.arvados.org/arvados.git/blobdiff_plain/d069271ec828654f9a6b656b04b40f229cfefb27..HEAD:/doc/install/singularity.html.textile.liquid
diff --git a/doc/install/singularity.html.textile.liquid b/doc/install/singularity.html.textile.liquid
deleted file mode 100644
index b3cbe593b6..0000000000
--- a/doc/install/singularity.html.textile.liquid
+++ /dev/null
@@ -1,40 +0,0 @@
----
-layout: default
-navsection: installguide
-title: Singularity container runtime
-...
-{% comment %}
-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.
-
-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@. 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.
-* 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.
-
-
-
$ singularity version
-3.5.2
-$ mksquashfs -version
-mksquashfs version 4.3-git (2014/06/09)
-[...]
-
-
-
-Then update @Containers.RuntimeEngine@ in your cluster configuration:
-
-
-