Add new GATK image built from nightly snapshot 2026-03-01#287
Open
Add new GATK image built from nightly snapshot 2026-03-01#287
Conversation
🐳 Expected TagsSome Dockerfiles have been modified in this PR. New tags are expected to be deployed.
|
MattWellie
reviewed
Mar 3, 2026
Build final stage from base Co-authored-by: Matt Welland <mattwellie@gmail.com>
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.
Build a GATK image using the GATK Nightly Snapshot from 2026-03-01, separately to the one in the gatk folder, which installs the latest GATK release (4.6.2.0).
The reason for building a new GATK image from the "unstable" nightly builds is because these builds include
htsjdk 4.3.0, while the latest release does not - meaning no support for CRAM 3.1 in the official release.The Dockerfile in this PR does things mostly the same as the other gatk image, except for a few differences.
PKG_CONFIG_PATHbefore themakecommand.curlnotwget- this resolved some issues with piping to stdout(A lot of credit for this goes to Gemini)