Optimize Docker image to fix CI memory issues #1333
Merged
Conversation
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
MaximeBICMTL
force-pushed
the
fix_docker_memory_issues
branch
2 times, most recently
from
4a2ea40 to
c0395a2
Compare
MaximeBICMTL
added
Category: Bug
MaximeBICMTL
force-pushed
the
fix_docker_memory_issues
branch
from
c0395a2 to
b8d7f84
Compare
cmadjar
approved these changes
Nov 15, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
Recently, CI integration tests have been failing due to the LORIS-MRI Docker image being too large for the GitHub Actions runner (see #1325 and #1332). This PR optimizes the LORIS-MRI Dockerfile to decrease the image size and make CI work again.
Results
Before:
After: