Image Pull Rate Limit Error on AKS

Summary

The user is experiencing an issue with pulling the Airbyte bootloader image from Docker Hub due to exceeding the pull rate limit, resulting in a 429 Too Many Requests error.


Question

Hi Team, Please help me on this issue deployed on AKS by helm “Failed to pull image “airbyte/bootloader:0.50.35”: failed to pull and unpack image “http://docker.io/airbyte/bootloader:0.50.35|docker.io/airbyte/bootloader:0.50.35”: failed to copy: httpReadSeeker: failed open: unexpected status code https://registry-1.docker.io/v2/airbyte/bootloader/manifests/sha256:1c8ebffaeab00e60fd139c1ee5d3ea2a180d64e58bb6201b3e2f7f5e2f478554: 429 Too Many Requests - Server message: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit



This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.

Join the conversation on Slack

['aks', 'helm', 'docker', 'image-pull', 'rate-limit', 'airbyte-bootloader']

https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/

you need to find your helm chart and check where to set imagePullSecrets in values.yaml
https://github.com/airbytehq/helm-charts

Another option is to pull all Docker images for Airbyte services (+ connectors) from Docker Hub, push them to Azure Container Registry and update all references in values.yaml

https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/

you need to find your helm chart and check where to set imagePullSecrets in values.yaml
https://github.com/airbytehq/helm-charts

Another option is to pull all Docker images for Airbyte services (+ connectors) from Docker Hub, push them to Azure Container Registry and update all references in values.yaml