We have been using the same version of a docker hub repository as the image of our bitbucket pipelines for 1 year. Suddenly, it begun failing and we don't know the reason.
The code below is at the top of the bitbucket-pipelines.yml file
The pipelines fails right after its beginning, with the following error.
rpc error: code = Unknown desc = failed to pull and unpack image "docker.io/juryvox/juryvox-react-test:latest": failed to copy: httpReaderSeeker: failed open: unexpected status code http://localhost:5000/v2/juryvox/juryvox-react-test/blobs/sha256:80e2dc61b67de22acb940d4bea02b2cd973abc3e7fd2bfd2fe1a486ce2dfde6f: 500 Internal Server Error
I have already checked if I am able to pull the repository from dockerhub using the same username and password that are set as bitbucket's repository variables, and it worked. I don't understand why it became a problem without any change neither at the container repository, nor at the bitbucket-pipelines.yml.
What could be causing this error?
similar issue since today:
rpc error: code = NotFound desc = failed to pull and unpack image "docker.io/library/maven:3.3.3-jdk-7": failed to unpack image on snapshotter overlayfs: failed to extract layer sha256:42755cf4ee95900a105b4e33452e787026ecdefffcc1992f961aa286dc3f7f95: failed to get reader from content store: content digest sha256:5c90d4a2d1a8dfffd05ff2dd659923f0ca2d843b5e45d030e17abbcd06a11b5b: not found
I had to make my docker image public to make it work. I think there is some bug with the communication between the repository variables and the pipelines instance. The code I posted worked for a long time, until I update my docker hub password. Then, I updated the repository variables with the new value and it stopped working, and the problem was not the password, because I copied pasted it on docker hub and it worked.
I hope my problem may help your team to find the bug, but I'm no longer interested in the answer.
Sorry for posting my problem at the wrong place.
I am getting a similar error:
rpc error: code = Unknown desc = failed to pull and unpack image "eu.gcr.io/lofty-seer-161814/othoz-docker-base:4.0.0": failed to resolve reference "eu.gcr.io/lofty-seer-161814/othoz-docker-base:4.0.0": failed to authorize: failed to fetch oauth token: Get https://eu.gcr.io/v2/token?scope=repository%3Alofty-seer-161814%2Fothoz-docker-base%3Apull&service=eu.gcr.io: dial tcp 22.214.171.124:443: i/o timeout
it happens sporadically. A restart goes OK once in a while.
I am getting a similar error:
rpc error: code = Unknown desc = failed to pull and unpack image "company.azurecr.io/custom-image:latest": failed to copy: read tcp XX.XX.XX.XX:XXXX->XX.XX.XX.XX:XXX: read: connection timed out
No solution has been found yet. Like Anton, I need to restart the pipeline when the error occur, and it works.
Does anyone found a clean solution on that ?
I am also facing the same issue since yesterday, though there are a couple of behaviours different in my case
1. Could not recall this happening before, have been running the same private image from Docker Hub for more than a year at least across different BB repos.
2. Restarting the pipeline does not make it work, and it is failing in all of these repos.
Note: Docker Hub Credentials are not changed. Able to login to Docker Hub using the same creds. Also used another pair of creds, still the same error!!
Hi everyone, We are looking to learn more about development teams’ workflows and pain points, especially around DevOps, integrations, administration, scale, security, and the related challeng...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events