Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Building the singularity container produces errors #38

Open
mattheww95 opened this issue Oct 23, 2024 · 2 comments
Open

Building the singularity container produces errors #38

mattheww95 opened this issue Oct 23, 2024 · 2 comments

Comments

@mattheww95
Copy link

Recently when running the command to pull the docker container that contains the databases (singularity pull docker://npbhavya/sphae:latest) I suddenly received a large number of errors after downloading the container downloaded and it was generating signatures.

A large number of fatal error were listed afterwards (see relevant picture), but sadly I could not get a screenshot with more information as my computer became unusable and required re-booting.
image

A collegue of mine has had similar issues while trying to download the container as well.

My computer specifiications are as follows:

Apptainer version (singularity): 1.2.2
OS: Ubuntu 22.04.3 LTS on Windows 10 x86_64
Kernel: 5.15.153.1-microsoft-standard-WSL2
Shell: bash 5.1.16
CPU: Intel i7-8665U (6) @ 2.112GHz
GPU: aa46:00:00.0 Microsoft Corporation Device 008e
Memory: 336MiB / 24038MiB

@npbhavya
Copy link
Collaborator

Hi,

I haven't testes the docker image on WSL, its working on mac and RedHat, so let me give that a try and get back to you. Meanwhile, sphae is available to download as both pip and conda packages as well.

Thank you,
Bhavya

@mattheww95
Copy link
Author

Thank you so much! The error only occured when I was converting the docker container to a singularity image, their may have been some issues on my computer with memory usage at the time, however my collegue had similar issues.

We are proceeding with using a conda installation for now but I just wanted to let you know about the issue we encoutered in case any one else does!

Please feel free to close the issue if you cannot re-create it, thank you for your time!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants