@kapa.ai All of a sudden, my airbyte cannot find a MySQL image it'd been using all alone. The error message is

Could not find image: airbyte/source-mysql:3.3.0

. Restarting airbyte server did not work. What do I do now?

This error means the worker can’t pull or access the connector image

airbyte/source-mysql:3.3.0

, even if it may exist locally or used to work before. Based on the docs and similar “Could not find image …” reports, here are the concrete steps you can try: 1. If you’re using a custom image registry (Kubernetes/Helm) Make sure the MySQL connector image is actually present in your registry and matches the exact name and tag:

bash    docker pull airbyte/source-mysql:3.3.0    docker tag airbyte/source-mysql:3.3.0 <http://ghcr.io/NAMESPACE/source-mysql:3.3.0|ghcr.io/NAMESPACE/source-mysql:3.3.0>    docker push <http://ghcr.io/NAMESPACE/source-mysql:3.3.0|ghcr.io/NAMESPACE/source-mysql:3.3.0>

and confirm

values.yaml

points to that registry (for example):

yaml    global:      image:        registry: <http://ghcr.io/NAMESPACE|ghcr.io/NAMESPACE>

If the registry is private, ensure the Kubernetes imagePullSecret is configured under

global.imagePullSecrets

. [[Custom registry](https://docs.airbyte.com/platform/enterprise-setup/implementation-guide#configure-a-custom-image-registry)] 2. If you’re running via

abctl

on kind (default for abctl) You must load the image into the kind cluster:

bash    docker pull airbyte/source-mysql:3.3.0    kind load docker-image airbyte/source-mysql:3.3.0 -n airbyte-abctl

[[Custom connector kind](https://docs.airbyte.com/platform/operator-guides/using-custom-connectors#loading-connector-docker-containers-into-kind)] 3. If you changed or cleaned Docker / volumes recently - Ensure Docker can still pull from Docker Hub (no new auth / rate‑limit issue) by running:

bash      docker pull airbyte/source-mysql:3.3.0

- If images/configs got partially wiped and Airbyte is in a bad state, a full reset can help (for local

docker-compose

deployments only, and note this deletes Airbyte’s internal DB and configs):

bash      docker-compose down -v      docker-compose up

[[Resetting Airbyte](https://airbyte.com/tutorials/creating-duckdb-destination-with-python)] 4. If you use a custom-built connector image Make sure the name and tag in the UI match the image you actually built and loaded to the runtime (Docker or kind), using the same

kind load

approach above if running in kind. [[Custom connector kind](https://docs.airbyte.com/platform/operator-guides/using-custom-connectors#loading-connector-docker-containers-into-kind)] If you share how you deployed Airbyte (Docker Compose, abctl/kind, Kubernetes/Helm, or something else), I can narrow this down further, but the knowledge sources do not provide more specific MySQL‑only troubleshooting beyond the generic “image not found” handling shown above.