Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

datalad config points to non-existent images

Open Beginner friendly
#172 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
65/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
python, shell
Domain
devops

Research direction

Start by comparing the image paths in .datalad/config with the files under images/neurodesk/; the issue lists seven configured paths that are missing. Check the repository’s image naming or update process to determine which paths should be corrected. Done when each image entry in the config points to an existing image.

Written by the indexing model from the issue text.

Description

I was trying to see how large are the latest datalad configured images to build a local cache for our pipelines, and noticed that .datalad.config is pointing to non-existent one.

ls -la  $(grep image .datalad/config | cut -d' ' -f 3) 1>/dev/null
ls: images/neurodesk/neurodesk-vesselapp--0.3.1.simg: No such file or directory
ls: images/neurodesk/neurodesk-delphi--0.0.2.simg: No such file or directory
ls: images/neurodesk/neurodesk-exploreasl--1.11.0.simg: No such file or directory
ls: images/neurodesk/neurodesk-b0map--1.0.0.post1.simg: No such file or directory
ls: images/neurodesk/neurodesk-arfiproc--1.0.0.post1.simg: No such file or directory
ls: images/neurodesk/neurodesk-afib1--1.6.0.post1.simg: No such file or directory
ls: images/neurodesk/neurodesk-acsrss--0.1.4.simg: No such file or directory
Dominant language
Python
Stars
32
Forks
18
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 ReproNim/containers

All issues in ReproNim/containers

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.