Summary
Error message ‘airbyte/source-shopify:2.5.0 not found locally’ when trying to synchronize destination with Airbyte and Digital Ocean. Image does not exist. Unexpected error while checking connection.
Question
Hello Everyone, while trying to synchronize destination I have this message, i allready pushed this update but it doesn’t seem to work, i USE airbyte with digital ocean :
2024-09-10 10:14:15 platform > airbyte/source-shopify:2.5.0 not found locally. Attempting to pull the image…
2024-09-10 10:14:15 platform > Image does not exist.
2024-09-10 10:14:15 platform > Unexpected error while checking connection:
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
["synchronize-destination", "airbyte", "digital-ocean", "error-message", "image-not-found"]
how did you deploy your airbyte?
on digital ocean through a droplet it was done by a previous person in the company
It looks like for some reason it cannot find Docker image and it doesn’t even try to pull from http://hub.docker.com|hub.docker.com
As I don’t know how it was deployed and configured, well… good luck with debugging. You need to ensure that it will pull Docker images properly. Something like in this thread:
https://stackoverflow.com/questions/57108005/how-to-login-to-docker-hub-on-the-command-line
Do you think the problem can come from there : Today, we are announcing that Docker Compose will be deprecated from future versions of Airbyte OSS after version 1.0 is released (expected in early August 2024).
The detailled article : https://github.com/airbytehq/airbyte/discussions/40599
No, deprecation is deprecation. Whatever deployment method is used (docker compose, abctl, helm charts) under the hood Docker images are pulled from http://hub.docker.com|hub.docker.com (or private Docker registry if you configure it that way). Airbyte is not controlling http://hub.docker.com|hub.docker.com, only Docker images are pushed there.
Please spend some time to figure out how this droplet was configured, and try to debug. Or just create a new droplet from scratch. Whatever works for you.