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

Error response from daemon: received unexpected HTTP status: 503 Service Unavailable #379

Closed
kapildev-trilogy opened this issue Nov 25, 2022 · 4 comments

Comments

@kapildev-trilogy
Copy link

kapildev-trilogy commented Nov 25, 2022

Log from my GH Actions:

Pull down action image 'ghcr.io/enricomi/publish-unit-test-result-action:v[2](https://github.com/trilogy-group/aurea-insidesales-telephony-5k/actions/runs/3549019607/jobs/5960896761#step:2:2).2.0'
  /usr/bin/docker pull ghcr.io/enricomi/publish-unit-test-result-action:v2.2.0
  Error response from daemon: received unexpected HTTP status: 50[3](https://github.com/trilogy-group/aurea-insidesales-telephony-5k/actions/runs/3549019607/jobs/5960896761#step:2:3) Service Unavailable
  Warning: Docker pull failed with exit code 1, back off 1.6[5](https://github.com/trilogy-group/aurea-insidesales-telephony-5k/actions/runs/3549019607/jobs/5960896761#step:2:5)5 seconds before retry.
  /usr/bin/docker pull ghcr.io/enricomi/publish-unit-test-result-action:v2.2.0
  Error response from daemon: received unexpected HTTP status: 503 Service Unavailable
  Warning: Docker pull failed with exit code 1, back off 1.93[7](https://github.com/trilogy-group/aurea-insidesales-telephony-5k/actions/runs/3549019607/jobs/5960896761#step:2:7) seconds before retry.
  /usr/bin/docker pull ghcr.io/enricomi/publish-unit-test-result-action:v2.2.0
  Error response from daemon: received unexpected HTTP status: 503 Service Unavailable
Error: Docker pull failed with exit code 1

I tried locally too and the same error persists -- so it might not be a network issue.

@davidlj95
Copy link

The action's Docker image is hosted in GitHub Container Registry. And seems it's having issues right now.

image

So guess we'll have to wait til gets fixed!

@quom
Copy link

quom commented Nov 25, 2022

It should be possible to add continue-on-error to the job step to avoid this failing your build.

Edit: I don't think this actually works. GitHub packages appear to be up now too.

@EnricoMi
Copy link
Owner

EnricoMi commented Nov 25, 2022

Again (#257, #273) one of those github issues: https://www.githubstatus.com/incidents/ljwdk6qml8z8.

All we can do is wait for GitHub to fix this.

@davidlj95
Copy link

Already fixed 4 me

@EnricoMi EnricoMi pinned this issue Nov 25, 2022
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

4 participants