Closed WangDong-ls closed 1 year ago
Well, the problem is that you have another application (a game?) installed that is also called Singularity. So when Nextflow tries to use the container system Singularity (Apptainer), it instead launches the other application.
You need to make sure, that Singularity does not point to the other application when you execute Nextflow. You can check with which singularity
on the terminal and ideally should install your applications within virtual environments. Then you can have a gaming environment where Singularity points to the game and a Nextflow environment, where it points to the container executor.
Running under Python 3.8.10 (default, Jun 22 2022, 20:18:18) [GCC 9.4.0]
pygame 1.9.6
Hello from the pygame community. https://www.pygame.org/contribute.html
Traceback (most recent call last):
File "/usr/games/singularity", line 11, in
load_entry_point('Endgame-Singularity==1.0b1', 'gui_scripts', 'singularity')()
File "/usr/lib/python3/dist-packages/singularity/init.py", line 106, in main
g.logfile = dirs.get_writable_file_in_dirs("error.log", "log")
File "/usr/lib/python3/dist-packages/singularity/code/dirs.py", line 220, in get_writable_file_in_dirs
write_dir = write_dirs[dir_name]
KeyError: 'log'
Yep, agree. This looks like some sort of install issue with Singularity. Closing this for now as it doesn't appear to be a pipeline issue. I would recommend running the pipeline with the test profile to ensure you can get it working; see point 4 here
Please feel free to join the nf-core Slack Workspace for any future questions/issues. We have an #rnaseq channel where you can get more real-time help.
Description of the bug
Command used and terminal output
No response
Relevant files
System information
No response