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
When I ran dmriqc_flow with scilus-1.5.0 on a cluster that loaded flexiblas automatically (Narval in my case), I unexpectedly discovered that Python (inside the container) looked through the host dir for flexiblas (BLAS and LAPACK) for some reason ( ~/.local/lib). It thus always ended up with the followring error:
ImportError: libflexiblas.so.3: cannot open shared object file: No such file or directory
I don't know whether it's a $PATH order error or something else.. See Nextflow's issue #248 for a similar issue on the matter.
One thing I know is that by setting the var env PYTHONNOUSERSITE to true, it prevents Python from using the Host's local cache and works flawlessly! That's the solution used by nf-core/rnaseq.
Another potential solution that is probably more robust and safer for many reasons would be to enable autoMounts but to prevent mounting the host home dir. However there might be other implications I'm not aware but that would isolate properly the container env. Note that I haven't tested this solution.
When I ran dmriqc_flow with scilus-1.5.0 on a cluster that loaded flexiblas automatically (Narval in my case), I unexpectedly discovered that Python (inside the container) looked through the host dir for flexiblas (BLAS and LAPACK) for some reason (
~/.local/lib
). It thus always ended up with the followring error:I don't know whether it's a $PATH order error or something else.. See Nextflow's issue #248 for a similar issue on the matter.
One thing I know is that by setting the var env
PYTHONNOUSERSITE
to true, it prevents Python from using the Host's local cache and works flawlessly! That's the solution used by nf-core/rnaseq.See last env var set in nextflow.config
Another potential solution that is probably more robust and safer for many reasons would be to enable autoMounts but to prevent mounting the host home dir. However there might be other implications I'm not aware but that would isolate properly the container env. Note that I haven't tested this solution.
That being said, this problem only happens because it uses nextflow v21. It was fixed in v23.07.0+) See warning in official doc here.
The text was updated successfully, but these errors were encountered: