-
Notifications
You must be signed in to change notification settings - Fork 0
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
Update Battenberg v2.2.9
Dockerfile
#9
Update Battenberg v2.2.9
Dockerfile
#9
Conversation
…GRCh37 and GRCh38)
I'll create /hot/software/image/docker-Battengberg after we release this docker image and move all relevant logs and test results to the dev dir of this repo. |
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.
Some comments:
Tested the image again, all works good. |
Image tested with ASCAT version specified. Test was successful. Test location same as before. |
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.
Added a few minor comments but otherwise, looks good to me. Anything else to add @yashpatel6 ?
ARG HTSLIB_VERSION=1.16 | ||
ARG ALLELECOUNT_VERSION=4.3.0 | ||
ARG IMPUTE2_VERSION=2.3.2 | ||
RUN mamba create -qy -p /usr/local \ | ||
-c bioconda \ | ||
-c conda-forge \ | ||
htslib==${HTSLIB_VERSION} \ | ||
cancerit-allelecount==${ALLELECOUNT_VERSION} \ | ||
impute2==${IMPUTE2_VERSION} |
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.
No need to worry about this in this PR but we may want to consider creating an image for each tool.
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.
@Faizal-Eeman can you create a GH issue on this?
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.
Issue #12 created.
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.
Looks fine to me, agreed on Taka's comment about trying to have fewer layers
Dockerfile
Outdated
RUN R -q -e 'devtools::install_github("Crick-CancerGenomics/ascat/[email protected]")' | ||
|
||
# Install Battenberg 2.2.9 | ||
RUN R -q -e 'devtools::install_github("Wedge-Oxford/[email protected]")' |
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.
We might also want to make ASCAT and Battenberg versions args rather than hard-coded here
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.
Seems to take a bit of dirty work to use ARG here as there are both single and double quotes. I'll update this in another PR later.
Reduced layers, verified the image with a successful test run. |
Description
Standardize Dockerfile and update Battenberg
v2.2.9
Closes #1
Closes #2
Testing Results
Docker Image Testing
docker run
command as described below.Test the Docker image with at least one sample. Verify the new Docker image works using:
Note: The sex of the sample was arbitrarily assigned to test the docker run.
My command:
Battenberg docker command was wrapped in an sbatch shell script and run on an F32.
sbatch /hot/user/mmootor/temp_files/battenberg/run/test_run_battenberg.sh
Log:
Test Cases
Checklist
Formatting
I have read the code review guidelines and the code review best practice on GitHub check-list.
The name of the branch is meaningful and well formatted following the standards, using [AD_username (or 5 letters of AD if AD is too long)]-[brief_description_of_branch].
I have set up or verified the branch protection rule following the github standards before opening this pull request.
File Updates
I have ensured that the version number update follows the versioning standards.
I have updated the version number in the
Dockerfile
,README.md
andmetadata.yaml
files.I have updated the dependencies and added my name to the maintainer list in the
Dockerfile
.I have updated the feature changes in the
README.md
(optional).I have added the changes included in this pull request to the
CHANGELOG.md
under the next release version or unreleased, and updated the date.GitHub Packages Auto Build Rules
I have not manually pushed this Docker image to the uclahs-cds container registry (
ghcr.io/uclahs-cds
) on GitHub.I have updated the
image_name
in themetadata.yaml
which is required by GitHub action to automatically build and push the image.