Docker Hub pull rate limits failing builds for 0.9.114 Docker images

[stanhu]

It appears https://github.com/oxidize-rb/rb-sys/actions/runs/14914597278 failed a number of builds due to Docker Hub pull rate limits. For example:

Running dive on ***/aarch64-linux-musl:sha-f5a504dc0759b0259836fe81037d568a4fed5370 with max wasted percent of 0.95
Unable to find image 'wagoodman/dive:latest' locally
docker: Error response from daemon: toomanyrequests: You have reached your pull rate limit as '***': dckr_jti_90kT_xQCKCaUIGyZSxdZ_MQIjm4=. You may increase the limit by upgrading. https://www.docker.com/increase-rate-limit

@ianks Can you retry?

[stanhu]

@ianks We're not able to build with rb_sys 0.9.114 at the moment due to the missing images:

rake-compiler-dock bash -c "bundle && RUBY_CC_VERSION=\"3.4.1:3.3.7:3.2.6:3.1.6\" bundle exec rake native:aarch64-linux-gnu pkg/gitlab-glfm-markdown-0.0.31-aarch64-linux-gnu.gem\n"
Unable to find image 'rbsys/aarch64-linux-gnu:0.9.114' locally
docker: Error response from daemon: manifest for rbsys/aarch64-linux-gnu:0.9.114 not found: manifest unknown: manifest unknown.

Could you click retry on the pipelines? It seems that the pipelines might need to cache a local image to build these images.

[stanhu]

It looks like 0.9.115 succeeded without hitting the rate limit: https://github.com/oxidize-rb/rb-sys/actions/runs/15028362093

I'll close this even though images for 0.9.114 are not available.