Conda is ok but singularity failed about fetchngs HOT 4 CLOSED

There may be a difference between setting HTTPS_PROXY for the host running Nextflow, but Nextflow starts several processes and containers without propagating environment variables (unless explicitly told), so perhaps the HTTPS_PROXY is not present inside the container.

Try going to the workdir indicated by the error and running .command.run. If you look at that script, you may be able to see where .command.run starts a Singularity container. See if you can hit any external network resource from inside that container.

from fetchngs.

Yep, that makes sense. You could try to export any network-type variables via the NF env scope to make them available within the container.

Did you find a solution to this @lindenb ? Could test independent of NF by running the command within the container and exporting the appropriate environment variables if you know what they are.

from fetchngs.

Did you find a solution to this @lindenb ?

@drpatelh not for now. I haven't tried nf-core since my first post :-) My resistance to frustration is quite low 😆

from fetchngs.

No worries @lindenb ! Ok, I will close for now and if you muster the courage to try again then please feel free to re-open if the problem persists.

from fetchngs.