rsnt_translations
56,420
edits
No edit summary |
No edit summary |
||
Line 331: | Line 331: | ||
<!--T:92--> | <!--T:92--> | ||
* as an <code>SIF</code> file, or | * as an <code>SIF</code> file, or | ||
* as a sandbox directory. | * as a sandbox directory. | ||
<!--T:93--> | <!--T:93--> | ||
<b><code>SIF</code> files</b> can contain multiple parts where each part is typically a <code>squashfs</code> filesystem (which are read-only and compressed). It is possible for <code>SIF</code> files to contain read-write filesystems and overlay images as well, but such is beyond the scope of this page | <b><code>SIF</code> files</b> can contain multiple parts where each part is typically a <code>squashfs</code> filesystem (which are read-only and compressed). It is possible for <code>SIF</code> files to contain read-write filesystems and overlay images as well, but such is beyond the scope of this page; see [http://apptainer.org/docs Apptainer's official documentation] on how to do such. Unless more advanced methods of building an image were used, the Apptainer <code>build</code> command produces a <code>SIF</code> file with a read-only <code>squashfs</code> filesystem when building images. This is the preferred option since the resulting image remains as-is since it is read-only, and the image is much smaller because it is compressed. Know that disk reads from that image are done very quickly. | ||
<!--T:94--> | <!--T:94--> | ||
<b>A sandbox directory</b> is a normal directory in the filesystem that starts out as empty | <b>A sandbox directory</b> is a normal directory in the filesystem that starts out as empty. As Apptainer builds the image, it adds to that directory the files, etc. needed in the image. The contents of a sandbox directory should only be accessed, updated, etc. through the use of Apptainer. One might need to use a sandbox directory in situations where one needs to have read-write access to the image itself in order to be able to update the container image. That said, if updates are infrequent, it is typically easier and better to use an <code>SIF</code> and when updates need to be done, build a sandbox image from the <code>SIF</code> file, make the required changes, and then build a new <code>SIF</code> file, e.g., | ||
<!--T:95--> | <!--T:95--> | ||
Line 351: | Line 351: | ||
<!--T:96--> | <!--T:96--> | ||
Using an <code>SIF</code> image is recommended as disk performance (from the container image) will be faster than storing each file, etc. separately on | Using an <code>SIF</code> image is recommended as disk performance (from the container image) will be faster than storing each file, etc. separately on our cluster filesystems, which are set up to handle large files and parallel I/O. Using an <code>SIF</code> file instead of a sandbox image will also only use a quota file count amount of 1 instead of thousands (some images will typically contain thousands of files and directories). | ||
<!--T:97--> | <!--T:97--> | ||
Many Linux | Many Linux distribution package managers require root permissions in order to use them. This implies that Apptainer version 1.0.x and the older Singularity cannot be used on compute clusters to build images as a normal user. Should such occur, [[Technical support submit a ticket]] asking for help to create that image or use a computer with Apptainer installed where you have root permissions. | ||
<!--T:98--> | <!--T:98--> |