Error setting up MySQL connector

Summary

Error log indicates image airbyte/source-mysql:3.7.2 not found locally while setting up MySQL connector


Question

Good morning Everyone, I am attempting to set up a mysql connector but I am getting the following log error, can someone please advise:

2024-09-17 13:52:25 [46mplatform[0m > Docker volume job log path: /tmp/workspace/4097107d-bf21-4624-85c4-502f9dd4f07b/0/logs.log
2024-09-17 13:52:25 [46mplatform[0m > Executing worker wrapper. Airbyte version: 0.63.13
2024-09-17 13:52:25 [46mplatform[0m > Using default value for environment variable SIDECAR_KUBE_CPU_LIMIT: ‘2.0’
2024-09-17 13:52:25 [46mplatform[0m >
2024-09-17 13:52:25 [46mplatform[0m > Using default value for environment variable SOCAT_KUBE_CPU_LIMIT: ‘2.0’
2024-09-17 13:52:25 [46mplatform[0m > Using default value for environment variable SIDECAR_KUBE_CPU_REQUEST: ‘0.1’
2024-09-17 13:52:25 [46mplatform[0m > Using default value for environment variable SOCAT_KUBE_CPU_REQUEST: ‘0.1’
2024-09-17 13:52:25 [46mplatform[0m > ----- START CHECK -----
2024-09-17 13:52:25 [46mplatform[0m >
2024-09-17 13:52:25 [46mplatform[0m > Checking if airbyte/source-mysql:3.7.2 exists…
2024-09-17 13:52:25 [46mplatform[0m > airbyte/source-mysql:3.7.2 not found locally. Attempting to pull the image…
2024-09-17 13:52:25 [46mplatform[0m > Image does not exist.
2024-09-17 13:52:25 [46mplatform[0m > Unexpected error while checking connection:
io.airbyte.workers.exception.WorkerException: Could not find image: airbyte/source-mysql:3.7.2
at io.airbyte.workers.process.DockerProcessFactory.create(DockerProcessFactory.java:117) ~[io.airbyte-airbyte-commons-worker-0.63.13.jar:?]
at io.airbyte.workers.process.AirbyteIntegrationLauncher.check(AirbyteIntegrationLauncher.java:147) ~[io.airbyte-airbyte-commons-worker-0.63.13.jar:?]
at io.airbyte.workers.general.DefaultCheckConnectionWorker.run(DefaultCheckConnectionWorker.java:71) ~[io.airbyte-airbyte-commons-worker-0.63.13.jar:?]
at io.airbyte.workers.general.DefaultCheckConnectionWorker.run(DefaultCheckConnectionWorker.java:44) ~[io.airbyte-airbyte-commons-worker-0.63.13.jar:?]
at io.airbyte.workers.temporal.TemporalAttemptExecution.get(TemporalAttemptExecution.java:138) ~[io.airbyte-airbyte-workers-0.63.13.jar:?]
at io.airbyte.workers.temporal.check.connection.CheckConnectionActivityImpl.lambda$runWithJobOutput$1(CheckConnectionActivityImpl.java:229) ~[io.airbyte-airbyte-workers-0.63.13.jar:?]
at io.airbyte.commons.temporal.HeartbeatUtils.withBackgroundHeartbeat(HeartbeatUtils.java:57) ~[io.airbyte-airbyte-commons-temporal-core-0.63.13.jar:?]
at io.airbyte.workers.temporal.check.connection.CheckConnectionActivityImpl.runWithJobOutput(CheckConnectionActivityImpl.java:214) ~[io.airbyte-airbyte-workers-0.63.13.jar:?]
at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103) ~[?:?]
at java.base/java.lang.reflect.Method.invoke(Method.java:580) ~[?:?]
at io.temporal.internal.activity.RootActivityInboundCallsInterceptor$POJOActivityInboundCallsInterceptor.executeActivity(RootActivityInboundCallsInterceptor.java:64) ~[temporal-sdk-1.22.3.jar:?]
at io.temporal.internal.activity.RootActivityInboundCallsInterceptor.execute(RootActivityInboundCallsInterceptor.java:43) ~[temporal-sdk-1.22.3.jar:?]
at io.temporal.internal.activity.ActivityTaskExecutors$BaseActivityTaskExecutor.execute(ActivityTaskExecutors.java:107) ~[temporal-sdk-1.22.3.jar:?]
at io.temporal.internal.activity.ActivityTaskHandlerImpl.handle(ActivityTaskHandlerImpl.java:124) ~[temporal-sdk-1.22.3.jar:?]
at io.temporal.internal.worker.ActivityWorker$TaskHandlerImpl.handleActivity(ActivityWorker.java:278) ~[temporal-sdk-1.22.3.jar:?]
at io.temporal.internal.worker.ActivityWorker$TaskHandlerImpl.handle(ActivityWorker.java:243) ~[temporal-sdk-1.22.3.jar:?]
at io.temporal.internal.worker.ActivityWorker$TaskHandlerImpl.handle(ActivityWorker.java:216) ~[temporal-sdk-1.22.3.jar:?]
at io.temporal.internal.worker.PollTaskExecutor.lambda$process$0(PollTaskExecutor.java:105) ~[temporal-sdk-1.22.3.jar:?]
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) ~[?:?]
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) ~[?:?]
at java.base/java.lang.Thread.run(Thread.java:1583) [?:?]
2024-09-17 13:52:25 [46mplatform[0m >
2024-09-17 13:52:25 [46mplatform[0m > ----- END CHECK -----
2024-09-17 13:52:25 [46mplatform[0m >



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

["mysql-connector", "error", "image-not-found", "airbyte/source-mysql:3.7.2"]

I thought about “Sync now” for connection. Ignore this for now, because you need to have source and destination working to create any connection.
Have tried to setup your connector again?

Hi, The problem still persist, the error log remains the same

docker pull airbyte/source-mysql:3.7.2 on that linux vm machine returns any errors?

No, It downloaded a newer image for airbyte/source-mysql:3.7.2. However the error persists

Can you check what is the result of ls -l /var/run/docker.sock?

your issue reminded me similar thread
https://airbytehq.slack.com/archives/C021JANJ6TY/p1720594246438009?thread_ts=1720435033.609549&cid=C021JANJ6TY

It returns the following:

srw-rw---- 1 root docker 0 Sep 17 18:37 /var/run/docker.sock

check this https://stackoverflow.com/questions/51342810/how-to-fix-dial-unix-var-run-docker-sock-connect-permission-denied-when-gro
maybe any of tips will work for you

I changed the permissions but the error persists

How your Airbyte was installed/deployed? abctl? helm charts? digital ocean droplet?

Looks like some docker login (or docker login <http://registry-1.docker.io|registry-1.docker.io>) is missing somewhere
https://stackoverflow.com/questions/57108005/how-to-login-to-docker-hub-on-the-command-line

Its an internal linux vm, it was deployed by pulling the git repo

This internal linux vm is some custom made image with Airbyte pre-installed or something?
Airbyte is running on Docker? Kubernetes?
Have you prepared this linux vm, or you got it from somebody else?

Its a vanilla ubuntu VM, Airbyte is running on docker

Did you use abctl to install Airbyte?

docker compose? run-ab-platform.sh?

Can you run docker login <http://registry-1.docker.io|registry-1.docker.io> on your linux vm and repeat synchronization in Airbyte?

Kindly explain what you mean by ‘repeat synchronization in Airbyte’

The result of ls -l /var/run/docker.sock

srwxrwxrwx 1 root docker 0 Sep 18 13:20 /var/run/docker.sock

Unfortunately I’m not able to reproduce this error, because I use macOS