Skip to content
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

environmentvariables from containers need to exposed through module load #175

Open
stebo85 opened this issue Apr 13, 2023 · 0 comments
Open
Assignees

Comments

@stebo85
Copy link
Contributor

stebo85 commented Apr 13, 2023

This problem affects for example FSL and SPM:

SPM doesn't run in a notebook, but when setting this it works:

os.environ['FORCE_SPMMCR']="1"
os.environ['SPMMCRCMD']="/cvmfs/neurodesk.ardc.edu.au/containers/spm12_r7771_20211206/spm12_r7771_20211206.simg/opt/spm12/run_spm12.sh /cvmfs/neurodesk.ardc.edu.au/containers/spm12_r7771_20211206/spm12_r7771_20211206.simg/opt/mcr/v97/ script"

-> this should be done using module load

Same for FSL:

os.environ["FSLDIR"]="/cvmfs/neurodesk.ardc.edu.au/containers/fsl_6.0.5.1_20221016/fsl_6.0.5.1_20221016.simg/opt/fsl-6.0.5.1/"

Should the module build script be creating these automatically?

  1. Go in the container: Figure out what's on the path (go away from DEPLOY_PATH -> because it's often forgotten)
  2. Figure out what environment variables are set inside the container -> Translate them to being set outside the container?
@stebo85 stebo85 self-assigned this Apr 13, 2023
@stebo85 stebo85 moved this to New in NeuroDesk Apr 13, 2023
@stebo85 stebo85 moved this from New to Active in NeuroDesk Apr 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Active
Development

No branches or pull requests

1 participant