-
Notifications
You must be signed in to change notification settings - Fork 638
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
Using nextflow inspect
with Singularity
#4433
Comments
Update to nextflow 23.10.0 ! |
This behaviour (the first example: So the message comes from here which is called here - the comment there says |
Yup, my outputs above are all from 23.10.0 |
Hiya. I'm seeing the same problem with Nextflow 23.10.0-5889 I was following #4069 and I'm pretty sure I tested it at some point and it was working with Singularity. So maybe a regression from when the integration with Wave was added ? |
Ok, it is solved! f5bb829 |
The new
nextflow inspect
command is working nicely with Docker, but there is some odd behaviour for singularity.Requires wave, but shouldn't need to
We don't need to build the Singularity container here, it's already hardcoded in the script. We just want the URI. Is there any way that we can get to it? Source here.
Crashes if wave installed but no singularity
When I try locally, I get a different error - probably related:
Here it's not trying to use Wave, but it is trying to do
singularity pull
on the image, when I'm only asking to return the URI.The text was updated successfully, but these errors were encountered: