Upgrading from 0.40.26 to 0.41.0 on Docker

  • Is this your first time deploying Airbyte?: No
  • OS Version / Instance: Ubuntu 20.04 (LTS) x64
  • Memory / Disk: you can use something like 16Gb / 320Gb
  • Deployment: Docker
  • Airbyte Version:
  • Source name/version: 0.40.26
  • Destination name/version: 0.41.0
  • Step: docker-compose down, install docker compose plugin, wget new airbyte version from master (get docker_compose.yml and .env files) , docker compose up
  • Description:
    Cannot upgrade from 0.40.26 to 0.41.0 on Docker running on Ubuntu 20.04 x64.
    I followed the usual guide here 1 making sure I installed first docker compose plugin following this doc 1 from repository doing

sudo apt-get update

sudo apt-get install docker-compose-plugin

Version was correctly installed by checking docker compose version.
I then got the new airbyte version by running :

wget -N https://raw.githubusercontent.com/airbytehq/airbyte/master/{.env,docker-compose.yaml}

followed by docker compose up note the new syntax to use docker compose plugin instead of docker-compose up.

However it seems worker fails to build it is looking for a flags.yml file to complete , this file is required as part of the worker config set in the docker_compose.yml it seems to have been added in version v0.40.30
Any idea of what process should I follow to make sure I can safely upgrade to 0.41.0 ?

Hello there! You are receiving this message because none of your fellow community members has stepped in to respond to your topic post. (If you are a community member and you are reading this response, feel free to jump in if you have the answer!) As a result, the Community Assistance Team has been made aware of this topic and will be investigating and responding as quickly as possible.
Some important considerations that will help your to get your issue solved faster:

  • It is best to use our topic creation template; if you haven’t yet, we recommend posting a followup with the requested information. With that information the team will be able to more quickly search for similar issues with connectors and the platform and troubleshoot more quickly your specific question or problem.
  • Make sure to upload the complete log file; a common investigation roadblock is that sometimes the error for the issue happens well before the problem is surfaced to the user, and so having the tail of the log is less useful than having the whole log to scan through.
  • Be as descriptive and specific as possible; when investigating it is extremely valuable to know what steps were taken to encounter the issue, what version of connector / platform / Java / Python / docker / k8s was used, etc. The more context supplied, the quicker the investigation can start on your topic and the faster we can drive towards an answer.
  • We in the Community Assistance Team are glad you’ve made yourself part of our community, and we’ll do our best to answer your questions and resolve the problems as quickly as possible. Expect to hear from a specific team member as soon as possible.

Thank you for your time and attention.
The Community Assistance Team

@marcosmarxm Any one in the team to help us on this one ?

The new documentation was updated. Running the new shell script instead of running commands directly solves the issu.