nf-core / nf-core/tools

Failed to find existing container image with 'nf-core modules create'

Open
#3,514 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Python
Stars
322
Forks
255
Avg merge
2d 3h
Merged PRs (30d)
5

Description

Description of the bug

Hi!

I was trying to create a module for the tool MetaCache, which exists on bioconda, quay.io biocontainers and the singularity repository, but it didn't fill any container URL.

Maybe related:

  1. docker pull quay.io/biocontainers/metacache:<tag> only works with the full tag (e.g. 2.5.0--h077b44d_0), not with a tag such as latest or 2.5.0;
  2. mulled-search from galaxy-tool-util package also failed to find anything at quay.io.
  3. the page https://quay.io/repository/biocontainers/metacache?tab=info says “No build have been run for this repository”

Could be a problem with quay.io?

Command used and terminal output
$ nf-core modules create metacache/build

...
INFO     Using Bioconda package: 'bioconda::metacache=2.5.0'                                                                        
INFO     Could not find a Docker/Singularity container (Could not find singularity container for metacache)                         
WARNING  Could not find a bio.tools ID for 'metacache'
...
System information

Ubuntu 20.04
Python 3.10.2
nf-core 3.2.0

Contributor guide

Open the contributing guide

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.

Research direction

Start by reproducing nf-core modules create metacache/build with the reported nf-core 3.2.0 environment and compare the Bioconda, quay.io Biocontainers, and Singularity lookups. Check the related mulled-search behavior and determine whether the module creation flow should discover the full container tag or report the registry limitation clearly.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, python
Domain
cli, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.