-
Notifications
You must be signed in to change notification settings - Fork 1
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
Interactive container working differently than automatic execution #69
Comments
My first guess is this looks like a nipype bug to me, theres some unusual magic happening in nipype with etelemetry
Maybe try setting |
Since nipype is doing some unusual load logic, maybe try |
sorry -- too much text.. what is the meanwhile followed up on IBT-FMI/SAMRI#119 (comment) |
@asmacdo oh god. Thank you so much for bringing up that variable, I now remember everything. So yes, nothing is broken, I just forgot some finer points regarding how to use it:
We need to run But now that I hit this snag (again), maybe we could do something about it? |
According to ChatGPT Invoking /bin/bash without -l (or --login) starts a non-login shell. Non-login shells do not automatically source /etc/profile or the user's .profile, .bash_profile, etc. They typically source ~/.bashrc. So I guess you could add -l and see if that does it |
As a short preface, the interactive container is not really needed for this study, it's just a shell entry point with possible utility for debugging.
This issue came to my attention via a user relying on the opfvta-reexecution container as a way to gain containerized access to SAMRI (since there's no SAMRI container yet).
SAMRI uses nipype, and as part of running the preprocessing analysis nipype is imported.
That works fine (at the beginning I quit as soon as the preporcessing started, but it would continue going).
However, if I enter the container and try to import either nipype or analogous submodules of nipype which SAMRI imports, that fails:
Any ideas what could be going on @yarikoptic @asmacdo
The text was updated successfully, but these errors were encountered: