-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Definition file for apptainer #1240
Comments
We found the following entries in the FAQ which you may find helpful:
Feel free to close this issue if you found an answer in the FAQ. Otherwise, please give us a little time to review. This is an automated reply, generated by FAQtory |
Will move this into a PR to be added to the code base: easier to find for others |
@all-contributors please add @monique2208 for code |
I've put up a pull request to add @monique2208! 🎉 |
@monique2208 I may try to actually incorporate this change in the dockerfile recipe directly so that there is only a single container definition for docker and apptainer (easier for maintenance) if you see that the image you build when pulling from dockerhub with apptainer is giving trouble again, reopen the issue. |
We use apptainer. I tried to directly convert the docker image, but this does not work because of the different ways docker and apptainer handle the home directory.
The issue is that home is not available when apptainer builds the container. The octave savepath function tries to write the new paths into the octaverc file in home by default, so it ends in the container root. But this file is not read again when the container runs. I converted the docker file into a definition file, where I specify that the new paths should be saved in a global octaverc file, so that home is not required.
I add it here if anyone is interested. I have done limited testing but I have not had issues so far.
apptainer/singularity definition file
The text was updated successfully, but these errors were encountered: