Issue with GA4 Connector Upgrade in Docker Deployment

Slack Knowledge Base Q&A Connector Development
, , , ,
1

Summary

User is experiencing inconsistent results when upgrading the GA4 source connector using a custom Docker image versus the Airbyte UI, despite both using the same image from Docker Hub.


Question

Dear Airbyte Community,

I’m encountering an interesting situation with my Airbyte deployment and would appreciate your insights.

Current Setup:

  • Running Airbyte via docker-compose
  • Needed to upgrade the GA4 source connector

Steps I’ve taken:

  1. Pulled the latest GA4 connector image from Airbyte Docker Hub
  2. Renamed the docker image to use a custom name
  3. Attempted to add the new source connector via Docker using this custom name
    • Result: Encountered an error (details below)
  4. Tried upgrading through Airbyte UI instead
    • Result: Successfully upgraded

What’s puzzling me is that both approaches (my custom named image and the UI upgrade) are using the identical image from Airbyte’s Docker Hub, yet they produce different results.

Has anyone encountered a similar situation or could explain why this might be happening?

Thank you in advance for your assistance.

Best regards


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

['docker-compose', 'ga4-connector', 'docker-image', 'airbyte-ui', 'upgrade-issue']
2

Just to be sure, did you run all operations on the same machine? What is the operating system of machine running Airbyte deployment?

More details are needed, e.g. logs from containers.

One of my guesses is error with pulling Docker image. Could be a problem with Docker socket and local version is not used, but tries to pull from Docker Hub.

Another guess, less likely, architecture mismatch.