Using docker wave container throws error message for some files
Nobody has claimed this yet.
- Dominant language
- Nextflow
- Stars
- 429
- Forks
- 1.1k
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 153
Description
Have you checked the docs?
Description of the bug
I was using the QUAST module in a workflow and got the following error. Trying to rerun with the latest biocontainer image (quay.io/biocontainers/quast:5.3.0--py313pl5321h5ca1c30_2) worked fine.
Command used and terminal output
Command error:
WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap.
terminate called after throwing an instance of 'std::system_error'
what(): Operation not permitted
terminate called after throwing an instance of 'std::system_error'
what(): Operation not permitted
/usr/local/bin/_activate_current_env.sh: line 35: 14 Aborted (core dumped) micromamba activate "${ENV_NAME:-base}"
Relevant files
No response
System information
nextflow version: 24.10.3
docker version: 24.0.2
Contributor 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.
Research direction
Start by reproducing the QUAST module failure with Nextflow 24.10.3 and Docker 24.0.2, using the container details in the report. Compare that run with quay.io/biocontainers/quast:5.3.0--py313pl5321h5ca1c30_2 and inspect the module's container configuration and activation output. Done means identifying the module or container incompatibility and verifying the result with a regression check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100