BraTS-GoAT 2025 container images (BraTS25_1A-1D) are not published on Docker Hub
@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
- Domain
- devops, infrastructure
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
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from BrainLesion/BraTS
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 74/100
BrainLesion/BraTS#200 ·
-
[FEATURE] 2024 challenge proceedings are released and need to be referenced correctlyPossibly taken @MarcelRosier claimed this 11 days ago. Openenhancement
Difficulty 1/5 Under an hour Newbie friendliness 55/100
BrainLesion/BraTS#198 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
BrainLesion/BraTS#191 ·
-
[FEATURE] Integration smoke-test suite for containerized algorithmsPossibly taken @MarcelRosier claimed this 40 days ago. Openenhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
BrainLesion/BraTS#185 ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 55/100
BrainLesion/BraTS#162 ·
All issues in BrainLesion/BraTS
Similar issues
-
[Bug]: reme CLI crashes when the running server used a relative config pathPossibly taken @nurlanmnn claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
agentscope-ai/ReMe#770 ·
Maintainers usually reply within 1 day
-
Pi: paused model calls are reported as "not signed in" when the model's provider comes from an extensionPossibly taken @balcsida claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
microsoft/TokenEconomizer#288 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 67/100
sickn33/agentic-awesome-skills#2437 ·
Maintainers usually reply within 1 day
-
site-bug triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ethereum/consensus-specs#5846 ·
Maintainers usually reply within 1 day