Skip to content

Commit

Permalink
Update singularity.md
Browse files Browse the repository at this point in the history
  • Loading branch information
fangpingmu authored Sep 24, 2024
1 parent 0fe41d1 commit 7e7d3c0
Showing 1 changed file with 3 additions and 2 deletions.
5 changes: 3 additions & 2 deletions docs/applications/singularity.md
Original file line number Diff line number Diff line change
Expand Up @@ -82,7 +82,8 @@ In this example, singularity will be used to run an instance of the [deepvariant

To pull the docker container:

```module load singularity/3.8.3
```
module load singularity/3.8.3
singularity pull --name deepvariant-1.3.0.sif docker://google/deepvariant:1.3.0
```
The singularity image is located in the install directory:
Expand Down Expand Up @@ -183,4 +184,4 @@ FAQ

### Why can't I use Docker?

Docker images are not secure becuase they allow users to gain root access to the compute nodes. Singularity effectively runs as the user running the command, and does not result in elevated access. Also, docker interacts with the slurm job scheduler in a way that causes resource requests and usages to not match up, making it difficult to keep job queueing fair for all users. In that the clusters are multi-user systems, we want to make sure people can work without worry that others are accessing their data or unfairly using up resources.
Docker images are not secure becuase they allow users to gain root access to the compute nodes. Singularity effectively runs as the user running the command, and does not result in elevated access. Also, docker interacts with the slurm job scheduler in a way that causes resource requests and usages to not match up, making it difficult to keep job queueing fair for all users. In that the clusters are multi-user systems, we want to make sure people can work without worry that others are accessing their data or unfairly using up resources.

0 comments on commit 7e7d3c0

Please sign in to comment.