rsnt_translations
56,420
edits
Apptainer: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 357: | Line 357: | ||
<!--T:98--> | <!--T:98--> | ||
Apptainer has a <code>--fakeroot</code> feature | Apptainer has a <code>--fakeroot</code> feature used to build and manipulate images. With versions efore Apptainer 1.1, one wanting to use this feature on a cluster requires [[Technical support submitting a ticket]] for a system administrator to consider adding that person so Apptainer's <code>--fakeroot</code> on a specific cluster, which may or not be possible. With Apptainer version 1.1, <code>--fakeroot</code> can be used without being formally added. | ||
<!--T:99--> | <!--T:99--> | ||
| Line 363: | Line 363: | ||
<!--T:100--> | <!--T:100--> | ||
If all you need is to use a Docker image as-is with Apptainer, often those images can be built and run without issues, e.g., without any need to have additional permissions or explicitly use <code>--fakeroot</code>. Should you need to modify the image after creating it, | If all you need is to use a Docker image as-is with Apptainer, often those images can be built and run without issues, e.g., without any need to have additional permissions or explicitly use <code>--fakeroot</code>. Should you need to modify the image after creating it, you may need elevated permissions to successfully do this, e.g., if the image's Linux distribution package manager requires such and you need to install a package using it. For this reason, the examples shown below assume one only needs to use a Docker image as-is. | ||
==Building a SIF image== <!--T:101--> | ==Building a SIF image== <!--T:101--> | ||