Issue with source connectors missing after Airbyte restart on AWS EC2

Slack Knowledge Base Q&A Platform Questions
, , , ,
1

Summary

Fresh installation of Airbyte on AWS EC2 leads to source connectors like Shopify going missing after restart or settings change. Error log shows ‘Could not find image’ for the missing connector. Workaround involves manually executing a docker pull command from SSH.


Question

Hi everyone,
I am facing an issue with airbyte fresh installation on AWS EC2 - where my source connectors which initially work ( ex: shopify)
automatically go missing - after a restart/ any settings change . And i need to pull them back again.

here’s the error log i’m getting
2024-06-05 09:05:46 platform >
11
2024-06-05 09:05:46 platform > ----- START CHECK -----
12
2024-06-05 09:05:46 platform >
13
2024-06-05 09:05:46 platform > Checking if airbyte/source-shopify:2.1.4 exists…
14
2024-06-05 09:05:46 platform > airbyte/source-shopify:2.1.4 not found locally. Attempting to pull the image…
15
2024-06-05 09:05:46 platform > Image does not exist.
16
2024-06-05 09:05:46 platform > Unexpected error while checking connection:
17
io.airbyte.workers.exception.WorkerException: Could not find image: airbyte/source-shopify:2.1.4

as a workaround i always have to execute a docker pull command from ssh . can anyone please help!!! :slight_smile:


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

["airbyte", "aws-ec2", "source-connectors", "shopify", "docker-pull", "error-log"]
2

Hi <@U076LECSZ8R> … I had the same issue, and I dont know if you figured this out on your own, but after restarting the EC2 instance I also had to manually start up the docker container: airbyte-docker-proxy-1 (docker start airbyte-docker-proxy-1). After doing this I was able to get my shopify connector to test successfully.

3

we had this - and found this - which helped: https://github.com/airbytehq/airbyte/issues/39337#issuecomment-2216908722

Looks like this PR should fix it one day https://github.com/airbytehq/airbyte-platform/pull/334/files