Apptainer: Difference between revisions
Jump to navigation
Jump to search
(→Links) |
|||
| Line 1: | Line 1: | ||
= General = | = General = | ||
== Accessing data outside the container == | |||
Containers are '''separated from the storage''' that is on the system. | |||
This is why they are containers. | |||
All the data that they need to run are inside the container. | |||
If one needs to get access to any data outside the container, one has to '''bind''' the external storage to the container. | |||
'''By default''', only few locations are bound to containers, including the '''home directory of the user''' who runs the container. | |||
To bind the <code>/work</code>, and <code>/bulk</code>, and <code>/scratch</code> file systems, | |||
you have to add the <code>-B</code> option to your '''apptainer command line'''. Like this: | |||
apptainer -B /work,/bulk,/scratch .... | |||
This change ensures that these file systems will be available for programs running from inside the container. | |||
= Links = | = Links = | ||
[[ARC Software pages]] | [[ARC Software pages]] | ||
Latest revision as of 19:59, 22 November 2024
General
Accessing data outside the container
Containers are separated from the storage that is on the system. This is why they are containers. All the data that they need to run are inside the container.
If one needs to get access to any data outside the container, one has to bind the external storage to the container. By default, only few locations are bound to containers, including the home directory of the user who runs the container.
To bind the /work, and /bulk, and /scratch file systems,
you have to add the -B option to your apptainer command line. Like this:
apptainer -B /work,/bulk,/scratch ....
This change ensures that these file systems will be available for programs running from inside the container.