You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I run sina within a docker container (I've tried quay.io/biocontainers/sina:1.7.1--h9aa86b4_0 and creating my own container; see below), I get the error:
02:38:59 [SINA] This is SINA 1.7.2.
02:38:59 [SINA] Unable to open ARB database "SILVA_138.1_SSURef_NR99_12_06_20_opt.arb".
02:38:59 [SINA] The ARB database you were trying to use is likely corrupted.
My job:
sina --threads 4 --turn \
--fasta-write-dna --lowercase none \
--intype fasta --outtype fasta \
--in $fasta \
--db SILVA_138.1_SSURef_NR99_12_06_20_opt.arb \
-o align.fna
If I run the same job outside of the container image:
wget https://github.com/epruesse/SINA/releases/download/v1.7.2/sina-1.7.2-linux.tar.gz
tar -pzxvf sina-1.7.2-linux.tar.gz
./sina-1.7.2-linux/sina --threads ${task.cpus} --turn \
--fasta-write-dna --lowercase none \
--intype fasta --outtype fasta \
--in $fasta \
--db $sina_db_arb \
-o align.fna
...the job completes successfully.
There seems to be something about running sina within a docker container that causes it to fail with the error: [SINA] Unable to open ARB database
Maybe it has something to do with ownership/permissions?
GB_open is in libARBDB.so - it's the "connect" function for ARB databases. Usually, if that throws an error, it really just couldn't open the file. As in, it's not there because you misspelled the path, it doesn't have the right permissions, or it's not actually an ARB database.
If I run
sina
within a docker container (I've triedquay.io/biocontainers/sina:1.7.1--h9aa86b4_0
and creating my own container; see below), I get the error:My job:
If I run the same job outside of the container image:
...the job completes successfully.
There seems to be something about running sina within a docker container that causes it to fail with the error:
[SINA] Unable to open ARB database
Maybe it has something to do with ownership/permissions?
The dockerfile for my own sina image:
Switching to
ubuntu:20.04
does not fix the issue.The text was updated successfully, but these errors were encountered: