Currently, almost every hour somebody is popping u...
# team-maintainers
m
Currently, almost every hour somebody is popping up with an
.command.run permission denied
issue in Docker, but also Singularity, for example here on Slack and also GitHub. Looking at the change in tools/3416 by ewels, it seems as if a problem in the default
nextflow.config
shipped with the pipeline template causes issues with certain newer Nextflow versions? Am I correct to assume that running the pipeline with a custom config with
nextflow run -c process_shell_fix.conf
… should mitigate the issue? Has anybody tried that already and can confirm that it works? At the moment I have no suitable setup at hand to test… If so, we should probably write a blog post about it, as it affect many users across several institutions and countries…
p
Is this the same thing that you were commenting on a few days ago @Mahesh Binzer-Panchal ?
To do with the clobber flag
I forget where that thread was now
m
The discussion accompanying your pull request is pretty comprehensive: https://github.com/nf-core/tools/pull/3416/files
p
Yeah but I thought that we had resolved it 😕
Another Slack thread about this here
Though I thought from that thread that it was Conda + Mac combo only 🤔 And the thread you linked is presumably Singularity + HPC. So maybe they are different things.
ok digging more, I think that the above is a different / separate thing
The GitHub issue you linked to is effectively solved, it's just that the fix hasn't been released yet
And I guess it's just surfacing again now because of the recent stable release of Nextflow 🫠
nod 1
🙏 1
🙏🏻 1
m
Yeah, not related to the
noclobber
.