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

[clemlesne]

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.

[OneCricketeer]

ghcr.io also throws 429's

[amitie10g]

ghcr.io also throws 429's

Using GitHub Actions workflow on a public repository?

[OneCricketeer]

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

[amitie10g]

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. I haven't seen HTTP 429 when pulling from Actions runners anymore.

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