Hi, I am running into timeout issues and would like to change the corresponding flag in https://github.com/airbytehq/airbyte-platform/blob/main/flags.yml#L10 in my docker compose setup. The

docker-compose.yml

file uses the

config

attribute to apply these variables. However, docker compose no longer supports this attribute:

WARNING: Some services (airbyte-cron, server, worker) use the 'configs' key, which will be ignored. Compose does not support 'configs'` configuration - use `docker stack deploy` to deploy to a swarm.

How can I increase the timeout in my docker compose setup? Ideally without changing the source code and building the project myself 🙂

Based on the information provided in the extracts, it seems that you can adjust the timeout settings by modifying environment variables in the

.env

file. For instance, in a Kubernetes setup, the

ACTIVITY_MAX_TIMEOUT_SECOND

variable was increased to handle timeout issues ([source](https://airbytehq.slack.com/archives/C021JANJ6TY/p1671223036014729)). However, the specific flag you mentioned in

flags.yml

is not directly discussed in the provided extracts. Therefore, I can't provide a confident answer on how to adjust this flag in a Docker Compose setup without modifying the source code. For more detailed information, you might want to check the [Airbyte documentation](https://docs.airbyte.com) or ask in the [Airbyte Slack community](https://airbytehq.slack.com).

I didn't see any reference to

ACTIVITY_MAX_TIMEOUT_SECOND

in the code, so I don't think it is related. Could you confirm, please?