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

Use GitHub Packages for storing containers to avoid HTTP 429 errors from Docker Hub in GitHub Actions #155

Open
clemlesne opened this issue Jan 2, 2024 · 4 comments

Comments

@clemlesne
Copy link

Quite a few times, GitHub Actions stops because Docker Hub triggers an HTTP 429 (too many request) error, like there: https://github.com/clemlesne/azure-pipelines-agent/actions/runs/7384635563/job/20087929649.

This could be solved by deploying the containers in GitHub packages, allowing lower latency, and no HTTP 429 errors. The packages could be deployed both in Docker Hub and GitHub packages.

@clemlesne clemlesne changed the title Use GitHub Packages for storing containers Use GitHub Packages for storing containers to avoid HTTP 429 errors from Docker Hub in GitHub Actions Jan 2, 2024
@OneCricketeer
Copy link

ghcr.io also throws 429's

@amitie10g
Copy link

ghcr.io also throws 429's

Using GitHub Actions workflow on a public repository?

@OneCricketeer
Copy link

@amitie10g Not sure? We're seeing it from an Artifactory mirror

@amitie10g
Copy link

I've used crane to clone both tonistiigi/binfmt and moby/buildkit into my GHCR account within all tags and platforms available, as a workarround for my own builds and anyone's usage.

jobs:
  build:
  steps:
  - name: Set up QEMU
      uses: docker/setup-qemu-action@v3
      with:
        image: ghcr.io/amitie10g/binfmt:latest
    - name: Set up Docker Buildx
      uses: docker/setup-buildx-action@v3
      with:
        driver-opts: |
          image=ghcr.io/amitie10g/buildkit:master

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

3 participants