Skip to content

Airbyte Temporal container can't start, dynamicconfig/development.yaml: no such file #28590

Closed Answered by marcosmarxm
awahuang asked this question in Connector Questions
Discussion options

You must be logged in to vote

Hello 👋 the issue was fixed. The cause was last week Airbyte upgrade Temporal version to use a more recent version of their service and also Airbyte started to use a dynamicconfig file. The file was added in the Docker compose but the .run-platform.sh script wasn’t updated.

What you need to do is update the run-ab-platform.sh script which now includes the new file.

More info #28629

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@awahuang
Comment options

Answer selected by marcosmarxm
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment