Closed bosterholz closed 3 years ago
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
I can confirm that the above example provided by @bosterholz works with s_3_path_style_access = true
setting in nextflow config.
However there is still the issue that S3 can not be used as work directory:
~/projects/nextflowtest> nextflow run nextflow.nf -w s3://nextflow/
N E X T F L O W ~ version 20.04.1
Launching `nextflow.nf` [distraught_elion] - revision: 0f7cb73c3f
WARN: Local executor only supports default file system -- Check work directory: s3://nextflow/
executor > local (1)
[1d/24d861] process > splitLetters [100%] 1 of 1, failed: 1 ✘
[- ] process > convertToUpper -
Error executing process > 'splitLetters'
Caused by:
java.lang.UnsupportedOperationException
Command executed:
printf 'Hello world!' | split -b 6 - chunk_
Command exit status:
-
Command output:
(empty)
Work dir:
s3://nextflow/1d/24d8619eac0b78ebc0bd7780149266
Tip: view the complete command output by changing to the process work dir and entering the command `cat .command.out`
The work directory structure was created in S3, containing the .command.run
and .command.sh
files.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Bug report
Expected behavior and actual behavior
Nextflow should be able to access the Swift Object Store through the S3 API middleware, which emulates the S3 REST API.
This does not seem to function. Every attempt produces a gateway time-out error.
Program output
error:
Gateway Time-out (Service: Amazon S3; Status Code: 504; Error Code: 504 Gateway Time-out; Request ID: null; S3 Extended Request ID: null)
.nextflow.log:
s3.nf
nextflow.config:
Working scripts
Tests with a
Minio-Client, s3curl.pl
or a Java test file fromaws-java-sdk-1.11.365
worked fine.S3Sample.java:
Environment