-
Notifications
You must be signed in to change notification settings - Fork 532
ENH: use neurodocker 0.4.1 + apt install afni #2707
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
Merged
Merged
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
2be7bf4
use neurodocker 0.4.1 + apt install afni
32c2f42
fix: put license in /opt/freesurfer-6.0.0-min/
da2fab0
use most recent neurodocker + activate conda env
4c5e76f
use newer neurodocker and neurodebian stretch
c5ff5e8
Merge remote-tracking branch 'upstream/master' into enh/neurodocker
4a29a2a
upgrade pybids to 0.6.5 from 0.5.1
2648de6
Merge remote-tracking branch 'upstream/master' into enh/neurodocker
fcaafaf
Merge remote-tracking branch 'upstream/master' into enh/neurodocker
23e6357
fix: prepend system libraries to LD_LIBRARY_PATH
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@kaczmarj What if we revert the
BASE_IMAGE
? If that helps, I think that would be decent evidence that it's a library version issue.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@effigies - i don't think that will help. the
apt-get update
calls will update to the latest neurodebian stretch sources. i tried using neurodebian snapshots from september 17, 2017 and from january 1, 2017, but both ran into the sameflameo
error. i'm going to try to use the nipype base image on dockerhub with the current nipype source code now.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@effigies - i used nipype's base image on dockerhub (i.e.,
nipype/nipype:base
) and still got theflameo
error. is it possible that nipype's code is causing this? could one of the inputs toflameo
be corrupted / malformed?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But it works on
master
, still, with the same inputs. There's something new in the build.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@kaczmarj Is there any chance of using a Debian snapshot from earlier, as well? If it's a libc update or similar that's causing the issue, that wouldn't be resolved by using a neurodebian snapshot.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
true, i'll try that now. i'm experimenting with updating packages in the current nipype py36 docker image and see if that will reproduce the error.