Issue updating Airbyte version in docker-compose script

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

Summary

The user is facing issues updating the Airbyte version in a docker-compose script due to a failure in pulling the airbyte-proxy from Docker Hub. They are seeking clarification on how the script should work if not all service versions are deployed to Docker Hub.


Question

Hey all, I’m running under docker-compose run-ab-platform.sh. I understand this is being deprecated but right now i have to update the version to enable deduplication on full refresh
however upgrading VERSION in the .env fail on trying pull airbyte-proxy from docker hub… how is the script meant to work if not all versions of services are deployed to docker hub?


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", "update", "airbyte-version", "deduplication", "full-refresh", "docker-hub", "service-versions"]
2

some Airbyte components are not used anymore and they are not built any longer for docker hub
airbyte-proxy was replaced with nginx ingress (installation by abctl)

two approaches:

  1. don’t use “global” VERSION, but specify the latest Docker image for every Airbyte component
  2. use VERSION only for those that are still updated and published, for other set the latest available version (tag with numbers X.Y.Z recommended)