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

Problems building singularity image: Authentication error. #8

Closed
orzechoj opened this issue May 23, 2018 · 6 comments
Closed

Problems building singularity image: Authentication error. #8

orzechoj opened this issue May 23, 2018 · 6 comments

Comments

@orzechoj
Copy link

I'm having problems building the singularity image for the ChIP-seq pipeline. I get the same error both on my macbook and running on Uppmax/Rackham.

$ singularity pull --name nfcore-chipseq.img docker://nf-core/ChIPseq 
WARNING: pull for Docker Hub is not guaranteed to produce the
WARNING: same image on repeated pull. Use Singularity Registry
WARNING: (shub://) to pull exactly equivalent images.
ERROR Authentication error, exiting.
Cleaning up...
ERROR: pulling container failed!

$ singularity pull --name nfcore-chipseq.img shub://nf-core/ChIPseq 
ERROR Cannot find image. Is your capitalization correct?

Looking at this page, perhaps the name should be docker://nfcore/ChIPseq (without the "-"): https://hub.docker.com/r/nfcore/chipseq/ But this gives the same results as above.

Building the old singularity image docker://scilifelab/ngi-chipseq still works ok.

@ewels
Copy link
Member

ewels commented May 23, 2018

Have you tried nfcore-chipseq? (All lower caps). I think this should work. Annoyingly, docker assumes that if it can’t find a repo then it must be private and that it’s an authentication problem. So bit of a misleading error.

Images aren’t pushed to shub currently. Need to fix the docs here.

Phil

@orzechoj
Copy link
Author

Well I got a different error message for nfcore-chipseq:

$ singularity pull --name nfcore-chipseq.img docker://nfcore-chipseq
WARNING: pull for Docker Hub is not guaranteed to produce the
WARNING: same image on repeated pull. Use Singularity Registry
WARNING: (shub://) to pull exactly equivalent images.
Docker image path: index.docker.io/library/nfcore-chipseq:latest
ERROR UNAUTHORIZED: authentication required
ERROR Check existence, naming, and permissions
Cleaning up...
ERROR: pulling container failed!

@ewels
Copy link
Member

ewels commented May 23, 2018

Sorry, should't reply on my phone! It's a slash, not a hyphen. No hyphens at all, all lower case:

$ singularity pull --name nfcore-chipseq.img docker://nfcore/chipseq

You can tell from the docker pull command in the box on the right on the image page which has the image path.

Phil

@orzechoj
Copy link
Author

Hmm, I'm still having the same problem 🤔

$ singularity pull --name nfcore-chipseq.img docker://nf-core/chipseq
WARNING: pull for Docker Hub is not guaranteed to produce the
WARNING: same image on repeated pull. Use Singularity Registry
WARNING: (shub://) to pull exactly equivalent images.
Docker image path: index.docker.io/nf-core/chipseq:latest
ERROR UNAUTHORIZED: authentication required
ERROR Check existence

@ewels
Copy link
Member

ewels commented May 24, 2018

You put a hyphen in again! It's nfcore/chipseq not nf-core/chipseq 😆 However, I confess that I did not test the command that I wrote above when I wrote it - I just tried it now and I get a similar error.

On closer inspection the reason for this becomes (embarassingly) clear. There are no image builds. So there's nothing to pull.

The last one failed during the R installation step. I remember now that I did see this I think, but we're currently rebuilding the entire container, so I figured that it wasn't worth looking into it any more.

Ok, so in summary:

  1. Sorry for making you test so many commands! 😆
  2. We've started making a nf-core python helper tool, and I will soon add a subcommand that will automatically handle all of this crap by looking at the pipeline code. So you will never have to go through this again.
  3. We will finish work on the new container soon I hope, at which point the nfcore/chipseq container will exist!
  4. For now, running with the scilifelab/ngi-chipseq container should be fine. All of the required software is there, though it doesn't reach the level of reproducibility that we're aiming for (but this repo doesn't have a stable release yet, so we'll get there).

Again, apologies for the half-responses over the past few days (I've been travelling around teaching on various courses). Thanks for testing! I'll close this now that we have an explanation I think.

Phil

@ewels ewels closed this as completed May 24, 2018
@orzechoj
Copy link
Author

Haha, ok good to have it sorted out. My test with scilifelab/ngi-chipseq container is still running, so it seems to work ok.

ScientistSMC added a commit to ScientistSMC/rnaseq that referenced this issue Oct 14, 2019
Received an error when trying to download and transfer the singularity image using the command located in the Singularity, Running Offline section. See below:

"[user]$ singularity pull --name nf-core-rnaseq-1.3.img docker://nf-core/rnaseq:1.3
WARNING: pull for Docker Hub is not guaranteed to produce the
WARNING: same image on repeated pull. Use Singularity Registry
WARNING: (shub://) to pull exactly equivalent images.
Docker image path: index.docker.io/nf-core/rnaseq:1.3
ERROR UNAUTHORIZED: authentication required
ERROR Check existence, naming, and permissions
Cleaning up...
ERROR: pulling container failed!"

I found a related issue posted in a different nf-core pipeline (see here nf-core/chipseq#8). And was able to fix the issue by removing the "-" in nf-core.
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