Closed rzelle-lallemand closed 1 month ago
I identified another package (which works fine on our other server) that triggers this error:
(qa) $ fastqc
perl: error while loading shared libraries: libperl.so: cannot open shared object file: No such file or directory
(qa) $ conda list | grep fastqc
fastqc 0.12.1 hdfd78af_0 bioconda
Please open an issue in bioconda. This is not the place for such a bug.
@isuruf, thanks, I wasn't sure where to report this.
After troubleshooting it looks our use of "chmod 2775 -R" on the conda directory caused the issue. We had been using this command to give other users the ability to install packages and create new environments (otherwise they kept running into conda cache permission issues). This seems to work fine on our old server, but on the new server setting the SGID caused the issue we reported here. Using "chmod 775 -R" instead solved the issue.
Solution to issue cannot be found in the documentation.
Issue
We're in the process of setting up a new VM (RHEL 9.4 with SELinux enabled) for use with conda. I installed Miniforge3 24.3.0-0 with the following per-user configuration:
I skipped the "defaults" channel as it's recommended here to avoid licensing requirements by conda: https://prefix.dev/blog/towards_a_vendor_lock_in_free_conda_experience
We installed the "blast" software (https://anaconda.org/bioconda/blast) in conda, but when we try to run this software we get errors like:
We first suspected SELinux but disabling it didn't help. I next discovered that the standalone version of blast (https://www.ncbi.nlm.nih.gov/books/NBK52640/) runs fine. After downloading and extracting https://ftp.ncbi.nlm.nih.gov/blast/executables/blast+/2.16.0/ncbi-blast-2.16.0+-x64-linux.tar.gz:
Could this be a conda/miniforge issue? We haven't seen this error for any other of our conda packages.
Installed packages
Environment info