Hello all, I'm in the process of deploying Airbyte...
# replication-troubleshooting
a
Hello all, I'm in the process of deploying Airbyte to GCP (Compute Engine) following the documentation provided here. When initially launching Airbyte (
docker compose up -d
), I am being presented with the error
invalid mount config for type "bind": bind source path does not exist: /home/ad/airbyte/configs/flags.yml
as the individual containers are being created (Screenshot attached). Any idea why this is occurring?
c
I had the same issue. I copied what they had in their master branch on github into ./configs/flags.yml and it began working properly: https://github.com/airbytehq/airbyte/blob/master/configs/flags.yml
✅ 7
a
thanks -- literally just tried this as you sent the message and it fixed on my end too :D
🫡 1
p
same issue and worked for me as well! thanks @Chris Pinchot
s
+1 had the same issue
u
Hello, I created the issue https://github.com/airbytehq/airbyte/issues/22144 to fix the problem!
✅ 1
f
Unfortunately, this does not work for me 😞
Any suggestions?
u
Flo, can you check the latest version of documentation? https://github.com/airbytehq/airbyte/pull/22158 fix the file locations https://github.com/airbytehq/airbyte/pull/22160 fix documentation
f
Did both. It works on my machine. Will try again in GCE in a few days, Thanks, @Marcos Marx (Airbyte)!
c
It is weird, but I had to download “flags.yaml” instead of “flags.yml” and change it to “flags.yml” myself. But if you see the github, there are flags.yml only :S
u
You should copy flags.yml file not flags.yaml file. The file is correct here: https://github.com/airbytehq/airbyte/blob/master/flags.yml
❤️ 1
r
I also just removed all reference to the flag config in docker-compose and it worked
👍 1
m
@Robert Put the correct should be update the docker-compose and docker and try to spin up Airbyte using the flags.yml!
r
@Marcos Marx (Airbyte) I'll try in the next version