PAPI Error code 2
I'm getting this error when running a workflow:
Task helloChipSeqPipeline.ChipSeqPipeline:NA:1 failed. The job was stopped before the command finished. PAPI error code 2. Execution failed: generic::unknown: pulling image: docker pull: running ["docker" "pull" "gcr.io/docker-215501/chipseq-pipeline"]: exit status 1 (standard error: "Error response from daemon: pull access denied for gcr.io/docker-215501/chipseq-pipeline, repository does not exist or may require 'docker login': denied: Permission denied for \"latest\" from request \"/v2/docker-215501/chipseq-pipeline/manifests/latest\".\n")
I've double checked that the name is correct but I'm not sure what else could be the problem.
Comments
7 comments
Hi Lleonard,
I'll be happy to take a look at this. Can you share the workspace where the issue occured with GROUP_FireCloud-Support@firecloud.org by clicking the Share button in your workspace (see the icon with the three dots at the top-right)?
1. Add GROUP_FireCloud-Support@firecloud.org to the User email field and press Enter on your keyboard
2. Click Save
Let me know the workspace name, as well as the relevant submission ID.
Would you also be able to provide me (jcerrato@broadinstitute.org) access to the docker so I can replicate the issue?
Kind regards,
Jason
I shared the workspace. The submission ID is 4d35a2ad-d726-4192-a40e-f11f28ed7291 and the workspace name is ChipSeq Pipeline. I added you as a Browser to my Google Cloud project, I'm not sure if that will provide the access you need or not.
Hi Lleonard,
Would you also be able to provide jcerrato@broadinstitute.org access to gcr.io/docker-215501/chipseq-pipeline so I can confirm it's a valid Docker? Can you confirm you are a member of the group that has access to this Docker? Have you been able to use this Docker in the past or is this your first time trying to use it?
Kind regards,
Jason
I'm not sure why you can't access it but I've changed your role to Editor so hopefully that works. Yes I'm a member of the group. I think I've used it it before.
Hi Lleonard,
I did a test with that Docker and ran into the same issue. I believe the issue is that because this is a private Docker image, you will need to make sure your Proxy Group address, found in your Terra profile, has permission to the Docker image. This is required for non-public Dockers because one of your Terra pet service accounts will be running the workflow on your behalf and attempting to pull the Docker image, rather than your email address.
Can you give your Proxy Group the same permissions you gave me and try running again?
Kind regards,
Jason
The error is gone now, thanks.
Hi Lleonard,
Glad to hear! If we can be of any further assistance, please let us know.
Kind regards,
Jason
Please sign in to leave a comment.