BraTS-GoAT 2025 container images (BraTS25_1A-1D) are not published on Docker Hub

Open
#189 4 comments 0 reactions 1 assignee View on GitHub

@PaulaTBz is already working on this.

Since Oct 27, 2026.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
docker, python

Research direction

Start with brats/data/meta/goat.yml to confirm the four image references, then inspect scripts/known_failures.yaml and the project's image publishing workflow. Determine how BraTS challenge images are built and published, and verify that all four referenced tags resolve before removing their expected failure entries.

Written by the indexing model from the issue text.

Description

The new verification suite cannot resolve the four BraTS-GoAT 2025 container images referenced in brats/data/meta/goat.yml:

  • brainles/brats25_goat_cmengynn:latest - BraTS25_1A (Meng-Yuan Chen, et al.)
  • brainles/brats25_goat_cmuh_aic:latest - BraTS25_1B (To-Liang Hsu, et al.)
  • brainles/brats25_goat_satushe:latest - BraTS25_1C (Vaidehi Satushe, et al.)
  • brainles/brats25_goat_stockholmfederation:latest - BraTS25_1D (Simone Bendazzoli, et al.)

All four return HTTP 404 from the Docker Hub API, and there is no brats25_goat_* repository in the brainles namespace at all.

Cross-check: the cmengynn team's image exists for the Pediatric track (brainles/brats25_ped_cmengynn:latest, same author), while the other three teams' images are absent under every prefix (cmuh_aic, satushe, stockholmfederation). This indicates the GoAT 2025 images were simply never pushed (rather than a naming mismatch in the registry).

Requested action: publish the four images under the referenced names/tags. They are currently listed in scripts/known_failures.yaml, which makes the verification suite report them as expected_fail; the entries can be removed once the images resolve.

Dominant language
Python
Stars
89
Forks
19
Avg merge
2d 23h
Merged PRs (30d)
4

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from BrainLesion/BraTS

All issues in BrainLesion/BraTS

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.