-
Notifications
You must be signed in to change notification settings - Fork 15
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
Download of sourmash and vibrant databases always fail #187
Comments
Hey, you could download the remaining docker/singularity files manually and store them at I know that's not the convenient solution but the fastest for now. In a quick google search I found the following:
I will install singularity on my workstation and replicate your command and check if I get the same error Best |
Hi Mike! Thanks you very much for your suppafast reply! Doing it that way, It worked! 😃 I noticed now that I was following the instructions for the install in the documentation:
And I needed to change the nexftlow version from 20.07.01 to 21.04. Perhaps singularity also needs to be updated to a more recent version? Could that be the cause of the issue? I can try to replicate the error in a new environment if that helps Sorry if my previous message sounded a bit rude, I was in a rush 😓 |
thats what this issue section is for :D, also I want to escape thesis writing so I installed waiting now for Vibrant |
when you have more time (tomorrow or so) you could try the latest singularty environment? and run the setup command and see if it will work then.. if yes I will update the documentation 👍🏽 |
#187 updated sourmash to newest docker container: `nanozoo/sourmash:4.5.0--e12a57a`
Command used:
I have tried more than 10 times, deleting folders, and caching dirs, and it always seems to fail, either in the Sourmash or the Vibrant download step. I have tried all the solutions proposed in the topics, but none of them are working.
The error that I get:
If I manually run the following line:
It works
so It doesn't seem to be a problem of the image pulling?
The text was updated successfully, but these errors were encountered: