The error message

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

indicates that Airbyte is unable to find the Docker image for the MySQL source connector. This could be due to a few reasons: 1. The Docker image is not available locally on your server. 2. There might be a network issue preventing Airbyte from pulling the Docker image from Docker Hub. Here are a few steps you can take to troubleshoot this issue: 1. Pull the Docker image manually: You can try to manually pull the Docker image using the following command:

bash docker pull airbyte/source-mysql:3.4.12

If the image is successfully pulled, try to restart Airbyte and see if the issue persists. 2. Check your network connection: If you're unable to pull the Docker image manually, there might be a network issue. Ensure that your server has a stable internet connection and is able to reach Docker Hub. 3. Check Docker Hub rate limits: Docker Hub imposes [rate limits](https://www.docker.com/increase-rate-limits) on image pulls. If you're hitting these limits, you might need to authenticate your Docker client to Docker Hub, which increases the rate limits. 4. Restart Airbyte: Some users have reported that restarting Airbyte resolves this issue. You can try this and see if it helps. If none of the above steps help, please provide more details about your setup or consider reaching out to the Airbyte community on [Slack](https://slack.airbyte.com/) or [GitHub](https://github.com/airbytehq/airbyte) for further assistance. Sources: - [Github Issue (open): Docker - Can't find/pull source-image during Sync > Original post Part 1](https://github.com/airbytehq/airbyte/issues/40642) - [Github Issue (closed): [source-mysql] deployment bug while setting up connection via mysql connector. Thanks > Original post Part 7](https://github.com/airbytehq/airbyte/issues/39332) - [Github Issue (closed): DOCKER COMPOSE : Could not find image: airbyte/ > Original post](https://github.com/airbytehq/airbyte/issues/37433) - [Github Issue (closed): WorkerException: Could not find image: airbyte/source-declarative-manifest:0.79.1 > Original post](https://github.com/airbytehq/airbyte/issues/37461) - [Github Issue (open): Unexpected error could not find image: Airbyte/*:version > Comments Part 2](https://github.com/airbytehq/airbyte/issues/39424)

To restart Airbyte on a Google Cloud Platform (GCP) Compute Engine instance, you can follow these steps: 1. Connect to your GCP instance via SSH. You can do this from your local terminal using the following command:

bash gcloud --project=$PROJECT_ID beta compute ssh $INSTANCE_NAME

Replace

$PROJECT_ID

with your GCP project ID and

$INSTANCE_NAME

with the name of your GCP instance. 2. Once you're connected to your GCP instance, navigate to the directory where you have Airbyte installed. If you followed the [official Airbyte deployment guide](https://docs.airbyte.com/deploying-airbyte/on-gcp-compute-engine), it should be in a directory named

airbyte

.

bash cd airbyte

3. Now, you can use Docker Compose to restart Airbyte. If you're not sure whether Docker Compose is running, you can stop it first using the following command:

bash docker-compose down

Then, you can start Airbyte using:

bash docker-compose up -d

This will start all the Airbyte services in the background. Please note that restarting Airbyte should not cause any data loss as the database data is persisted in the

airbyte_db

Docker volume, which is not removed by the

docker-compose down

or

up

commands ([source](https://discuss.airbyte.io/t/1381)). If you encounter any issues during this process, please provide more details or consider reaching out to the Airbyte community on [Slack](https://slack.airbyte.com/) or [GitHub](https://github.com/airbytehq/airbyte) for further assistance.

You're welcome! I'm glad to hear that your issue is resolved. If you have any more questions or run into any other issues with Airbyte in the future, don't hesitate to ask. Happy data integrating!