Use custom Busybox repository and image tag?

Connector Questions & Issues
,
1
  • Deployment: K8s via Helm
  • Airbyte Version: 0.40.28
  • Step: During a sync when worker pods are spinning up
  • Description: We’re experiencing Dockerhub rate limiting, so I would like to mirror the Busybox Docker image that is used by some pods into my ECR and reference it within our Helm chart. Is there anyway to provide a custom repository and image?
2

Hello there! You are receiving this message because none of your fellow community members has stepped in to respond to your topic post. (If you are a community member and you are reading this response, feel free to jump in if you have the answer!) As a result, the Community Assistance Team has been made aware of this topic and will be investigating and responding as quickly as possible.
Some important considerations that will help your to get your issue solved faster:

  • It is best to use our topic creation template; if you haven’t yet, we recommend posting a followup with the requested information. With that information the team will be able to more quickly search for similar issues with connectors and the platform and troubleshoot more quickly your specific question or problem.
  • Make sure to upload the complete log file; a common investigation roadblock is that sometimes the error for the issue happens well before the problem is surfaced to the user, and so having the tail of the log is less useful than having the whole log to scan through.
  • Be as descriptive and specific as possible; when investigating it is extremely valuable to know what steps were taken to encounter the issue, what version of connector / platform / Java / Python / docker / k8s was used, etc. The more context supplied, the quicker the investigation can start on your topic and the faster we can drive towards an answer.
  • We in the Community Assistance Team are glad you’ve made yourself part of our community, and we’ll do our best to answer your questions and resolve the problems as quickly as possible. Expect to hear from a specific team member as soon as possible.

Thank you for your time and attention.
Best,
The Community Assistance Team

4

We need to do the same thing b/c of rate limiting (we host a mirror for ourselves) and for reliability, too.

You can set custom image pointers for the system images by setting something like this in the values.yaml that will then set the right env vars on the worker.

Of course, you need to maintain your own mirror or pull-through-cache. We use a cdk-based sync system that uses AWS CodePipepline to do this based on our spec of what we want pulled. Refreshes via a lambda cron daily. Like this:

  extraEnv:
    - name: JOB_KUBE_SOCAT_IMAGE
      value: XXXXXXXXXXXX.dkr.ecr.us-east-1.amazonaws.com/dockerhub-mirror/alpine/socat:1.7.4.4-r0
    - name: JOB_KUBE_BUSYBOX_IMAGE
      value: XXXXXXXXXXXX.dkr.ecr.us-east-1.amazonaws.com/dockerhub-mirror/busybox:1.35
    - name: JOB_KUBE_CURL_IMAGE
      value: XXXXXXXXXXXX.dkr.ecr.us-east-1.amazonaws.com/dockerhub-mirror/curlimages/curl:7.87.0

You could also just use AWS’ ECR public image repo that mirrors most docker hub packages you’d need, if you’re pulling from AWS based boxes, there is no real rate limit for you if you have the basic ECR Public policy settings on the IAM role on the pulling process/workload. Like this (I have NOT tested these images):

worker:
  extraEnv:
    - name: JOB_KUBE_SOCAT_IMAGE
      value: public.ecr.aws/tvlk/alpine/socat:1.7.3.4-r0
    - name: JOB_KUBE_BUSYBOX_IMAGE
      value: public.ecr.aws/docker/library/busybox:1.35
    - name: JOB_KUBE_CURL_IMAGE
      value: public.ecr.aws/metaplay/curlimages/curl:7.85.0