Adding initial version of mosdepth WILDS Docker image#363
Merged
Conversation
tefirman
marked this pull request as ready for review
June 10, 2026 17:30
Member
Author
|
Relatively basic image, merging without additional review for a Tech Talk demo. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Type of Change
Description
Adds a new WILDS Docker image for mosdepth, a fast tool for calculating sequencing coverage depth from BAM/CRAM alignments at per-base, per-region, or windowed resolution (Pedersen & Quinlan, Bioinformatics 2018).
ubuntu:24.04/usr/local/bin/mosdepthapt-cache policy):wget,ca-certificates,zlib1g,libbz2-1.0,liblzma5,libcurl4t64— htslib's compression and HTTPS transitive depsmosdepth/Dockerfile_latest,mosdepth/Dockerfile_0.3.14,mosdepth/README.mdamd64_only_tools.txt— mosdepth added so the ARM64 build is skipped (see Additional Context)Testing
How did you test these changes?
make lint IMAGE=mosdepth— both Dockerfiles pass hadolint with no warningsmake build_amd64 IMAGE=mosdepth— bothDockerfile_latestandDockerfile_0.3.14build successfully and the in-build smoke testmosdepth --versionreportsmosdepth 0.3.14Did the tests pass?
Yes. Lint clean, build green, smoke test green on linux/amd64.
Checklist
Dockerfile_X.Y.ZorDockerfile_latest)README.mdis included/updated in the tool directorymake validate IMAGE=toolname(or manually built and verified)Additional Context
AMD64 only. Upstream mosdepth only publishes a
linux/amd64binary, so mosdepth is added toamd64_only_tools.txtto skip ARM64 builds — same pattern smoove already uses for the mosdepth it bundles.