Open Takk522 opened 8 months ago
The problem has been solved when I used 'sudo apptainer ...'. However, a new problem has appeared, as shown below. I tried to use the absolute path of the .ffindex file, but it didn't solve the problem. I am sure the file truly exists.
You can use binding to allow the container access to your file system: https://chat.openai.com/share/55bea319-d3ac-4c4b-bc2d-e639bc963a8d
Hello! I am also trying to run the container on our HPC system and I am running into a similar problem (first bug reported on this issue, and I am too a beginner singularity/apptainer user). As a user, I naturally cannot use sudo on our cluster. Would it be possible to have access to the container creation file ? I did't find one in the repo, my apologies if I missed something. Otherwise, would it be possible to have a list of directories that I would have to bind inside of the container to the external databases and weights saved in separate directories inside of our cluster ?
The provided container will not run on CentOS-7 as CONFIG_LZ4
is not defined in /boot/config-3.10.0-1160.*
The container also does not run on Ubuntu 20.04
hello, if the container is not working you could consider using the mamba environment set up by amorehead
I am not familiar with the apptainer. When encountered a fatal error like this, how could I deal with it? (ps. my apptainer version is 3.19.1)