User Guide¶
- Quick Start
 - Introduction
- Welcome to Singularity!
 - A High Level View of Singularity
 - The Singularity Usage Workflow
 - Support
 - About
 
 - Installation
- Before you begin
 - Install from a tag
 - Install a specific release
 - Install the development branch
 - Remove an old version
 - Install on Windows
 - Install on Linux
 - Install on Mac
 - Requesting an Installation
 
 - Build a Container
 - Build Environment
 - Container Recipes
 - Singularity Flow
 - Bind Paths and Mounts
 - Persistent Overlays
 - Running Services
 - Container Checks
 - Environment and Metadata
 - Reproducible SCI-F Apps
 - Singularity and Docker
 - Troubleshooting
 - Appendix
 - Contributing
 - FAQ
- General Singularity Info
 - Basic Singularity usage
- Do you need administrator privileges to use Singularity?
 - What if I don’t want to install Singularity on my computer?
 - Can you edit/modify a Singularity container once it has been instantiated?
 - Can multiple applications be packaged into one Singularity Container?
 - How are external file systems and paths handled in a Singularity Container?
 - How does Singularity handle networking?
 - Can Singularity support daemon processes?
 - Can a Singularity container be multi-threaded?
 - Can a Singularity container be suspended or check-pointed?
 - Are there any special requirements to use Singularity through an HPC job scheduler?
 - Does Singularity work in multi-tenant HPC cluster environments?
 - Can I run X11 apps through Singularity?
 - Can I containerize my MPI application with Singularity and run it properly on an HPC system?
 - Why do we call ‘mpirun’ from outside the container (rather than inside)?
 - Does Singularity support containers that require GPUs?
 
 - Container portability
 - Misc