trying to upgrade airbyte oss, getting this error running abctl @kapa.ai WARNING Back-off pulling image "airbyte/bootloader:2.0.1" WARNING Back-off pulling image "airbyte/bootloader:2.0.1" WARNING Encountered an issue deploying Airbyte: Pod: airbyte-abctl-workload-launcher-8c54b4cd-pqz7z.18a196b20d98c0c4 Reason: Unhealthy Message: Readiness probe failed: HTTP probe failed with statuscode: 503 Count: 44 WARNING Back-off pulling image "airbyte/bootloader:2.0.1" WARNING Back-off pulling image "airbyte/bootloader:2.0.1" WARNING Back-off pulling image "airbyte/bootloader:2.0.1" WARNING Back-off pulling image "airbyte/bootloader:2.0.1

The errors you're seeing indicate two related issues: 1.

ImagePullBackOff

/

Back-off pulling image "airbyte/bootloader:2.0.1"

– Kubernetes cannot pull the required Docker images from Docker Hub. 2. Readiness probe failing (503) – The workload launcher is unhealthy, likely because the bootloader never completed successfully (it's the first service to start). Most Likely Cause: Docker Hub Rate Limiting The

ImagePullBackOff

error is most commonly caused by Docker Hub pull rate limits being hit. [GitHub Issue] Steps to Resolve 1. Verify you can pull the image manually:

docker pull airbyte/bootloader:2.0.1

If this fails, it confirms a network/rate-limit issue. [GitHub Issue] 2. If it's a rate limit issue, wait up to 6 hours for the limit to reset, then clean up and retry:

abctl local uninstall
abctl local install --host domain.org

[GitHub Issue] 3. Check for network/proxy issues – If you're behind a corporate proxy or firewall, it may be blocking Docker Hub access. [GitHub Issue] 4. If the bootloader still fails after images are pulled, note that bootloader failures are generally related to the

airbyte-bootloader

not being able to connect to the

airbyte-db

service. Using

abctl

version

>0.15.0

will print service logs to help diagnose the root cause. [Troubleshooting abctl] In short, start by confirming you can manually pull

airbyte/bootloader:2.0.1

— that will tell you whether it's a connectivity/rate-limit problem or something deeper. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.