Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

container creation failed while running on test data and singularity #715

Closed
4 tasks done
GuidoBarzaghi opened this issue Oct 19, 2021 · 1 comment
Closed
4 tasks done
Labels
bug Something isn't working

Comments

@GuidoBarzaghi
Copy link

Check Documentation

I have checked the following places for your error:

Description of the bug

Hello! Similarly to #494, I have been having issues running the rnaseq pipeline on the test dataset using singularity. Up to now, I've been playing around with various versions of both the rnaseq pipeline, nextflow, singularity and even squashfs-tools. Nothing seems to help though.

Steps to reproduce

Steps to reproduce the behaviour:

  1. Command line: nextflow run nf-core/rnaseq -r 3.4 -profile test,singularity
  2. See error: FATAL: container creation failed: mount /proc/self/fd/13->/var/singularity/mnt/session/rootfs error: while mounting image /proc/self/fd/13: kernel reported a bad superblock for squashfs image partition, possible causes are that your kernel doesn't support the compression algorithm or the image is corrupted

Expected behaviour

I would expect the pipeline to create the container and allow for the job to be run

Log files

Have you provided the following extra information/files:

  • The command used to run the pipeline
  • The nextflow.log file

System

  • Hardware: HPC
  • Executor: slurm
  • OS: CentOS Linux
  • Version 7.6.1810

Nextflow Installation

  • Version: 21.04.3 build 5560

Container engine

  • Engine: Singularity
  • version: 3.9.0-rc.1

Additional context

@GuidoBarzaghi GuidoBarzaghi added the bug Something isn't working label Oct 19, 2021
@GuidoBarzaghi
Copy link
Author

Assigning fresh folders to the following solved the issue

  • SINGULARITY_CACHEDIR
  • SINGULARITY_TMPDIR
  • NXF_SINGULARITY_CACHEDIR
  • NXF_HOME

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant