-
Notifications
You must be signed in to change notification settings - Fork 194
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
Singularity pull fails #206
Comments
copied my answer from nf-core/rnaseq#311 in here for clarification: Hey @ScientistSMC ! thank you for submitting your first PR to nf-core/rnaseq. However, we moved the central documentation to our main webpage as downloading Singularity images for offline usage is something not really different across pipelines, which is why we centralized the docs for this. However, looking up whether this is already correctly stated on our webpage, I just figured out that it's not :-( See this section over here: https://nf-co.re/usage/installation#singularity (which still states the Looking at the repository of nf-core for the webpage, I found that this looks different in the markdown files we use: https://github.com/nf-core/nf-co.re/blob/master/markdown/usage/local_installation.md @ewels I believe this didn't roll out on the webpage as @ScientistSMC found out! |
@apeltzer @ScientistSMC This indeed needs a fix! See #203 Need to create a PR to the website repo asap now that it's been observed twice in a week! 😅 |
It is a bit weird that the markdown document is already fixed but apparently the webpage didn't update? |
Ah, but the bug is in a different page: |
Fixed in #207 |
Tried to setup Singularity (for offline use) using the instructions in the installation.md file but it failed. See below:
But I was able to get it working after editing the docker image path to remove the "-" from nf-core based on a similiar issue in another nf-core pipeline (see here: nf-core/chipseq#8). See below:
Created a pull request to remove the "-" in the installation.md document.
The text was updated successfully, but these errors were encountered: