6 merge requests!368Update prace.md to document the change from qprace to qprod as the default...,!367Update prace.md to document the change from qprace to qprod as the default...,!366Update prace.md to document the change from qprace to qprod as the default...,!323extended-acls-storage-section,!196Master,!180Singularity
@@ -9,11 +9,11 @@ Singularity also allows you to leverage the resources of whatever host you are o
* No user contextual changes or root escalation allowed
* No root owned daemon processes
These documentation are for Singularity Version 2.4 and newer.
This documentation is for Singularity version 2.4 and newer.
## Using Docker Images
Singularity can import, bootstrap, and even run Docker images directly from [Docker Hub](https://hub.docker.com/). You can easily run RHEL7 like this:
Singularity can import, bootstrap, and even run Docker images directly from [Docker Hub](https://hub.docker.com/). You can easily run RHEL7 container like this:
In this case, Image is downloaded from Docker Hub, extracted to a temporary directory and singularity interactive shell is invoked. This procedure can take a lot of time, especially for larger images.
In this case, image is downloaded from Docker Hub, extracted to a temporary directory and Singularity interactive shell is invoked. This procedure can take a lot of time, especially with large images.
## Creating Own Image From Docker Image
## Importing Docker Image
Singularity containers can be in three different formats:
...
...
@@ -40,7 +40,7 @@ Singularity containers can be in three different formats:
* writable **ext3** (--writable option)
* writable **(ch)root directory** (--sandbox option) - best for development
Squashfs and (ch)root directory image can be built from docker source directly on the cluster, no root privileges are needed. Creating native singularity image is strongly recommended due to the speed of launching the container.
Squashfs and (ch)root directory images can be built from Docker source directly on the cluster, no root privileges are needed. It is strongly recomended to create native Singularity image to speed up the launch of the container.
```console
hra0031@login4:~$ml Singularity
...
...
@@ -63,7 +63,7 @@ Cleaning up...
## Launching the Container
The interactive shell can be invoked by the `singularity shell` command. This is useful for development purposes. To make changes inside the container permanent use `-w | --writable` option.
The interactive shell can be invoked by the `singularity shell` command. This is useful for development purposes. Use the `-w | --writable` option to make changes inside the container permanent.
Singularity image can contain a runscript. This script is executed inside container after the `singularity run` command is used. The runscript is mostly used to run an application for which is the container build, in the following example it is `fortune | cowsay` command.
Singularity image can contain a runscript. This script is executed inside the container after the `singularity run` command is used. The runscript is mostly used to run an application for which the container is built. In the following example it is `fortune | cowsay` command.
```
hra0031@login4:~$ singularity run ubuntu.img
...
...
@@ -102,10 +102,10 @@ hra0031@login4:~$ singularity run ubuntu.img
## Accessing /HOME and /SCRATCH Within Container
By default, user home directory is mounted inside the container, therefore you can access your files directly. If you need access to **/SCRATCH** storage for your computation, this must be mounted by `-B | --bind` option.
User home directory is mounted inside the container automatically. If you need access to **/SCRATCH** storage for your computation, this must be mounted by `-B | --bind` option.
!!!Warning
Be aware, that the mounted folder has to exist inside the container or the container image has to be writable!
The mounted folder has to exist inside the container or the container image has to be writable!
