Closed scheckley closed 1 year ago
Discussed also on slack, probably an issue with Azure virtual machine
?
Turned out to be an issue with Docker - symbolic links don't work for mounted storage, similar to this issue on stack overflow. Not related to Nextflow or ampliseq.
Running with the Docker option on a folder of fastq files produces a file not found error during the cutadapt process. The pipeline completes without any errors when using the Singularity option. Python stack trace is enclosed below:
Not sure if this is docker configuration error, or a problem with the symbolic linking in rename_raw_data_files.nf not being visible from inside the container? The fastq files are located in a directory mounted as /data/Fastq/ on an Azure virtual machine which Nextflow is configured to read from in the --input option.
Thanks.