I am getting an error stating unable to resolve host airbyte temporal . This happened when I tried upgrading our airbyte deployment. I ahve tried running all the commands as mentioned in documentation yet while I write docker compose up code gets into loop . I have stopped it and tried running./run-ab-platform.sh -b though it is executed but when I try accessing the UI it's stays server is not available. I have tried changing the OS previously debian 11 to Debian 10 yeth the issue persist. Please help

Based on the information provided in the extracts, it seems like you're encountering an issue with the Airbyte Temporal service during the upgrade process. This could be due to a variety of reasons, including network issues, Docker service problems, or configuration errors. Here are a few steps you can try based on the information from the extracts: 1. Ensure Docker Compose V2 is installed: Airbyte version 0.40.27 or later requires Docker Compose V2 to be installed before upgrading. You can check this by running

docker compose version

in your terminal. If it's not installed, you can follow the installation guide [here](https://docs.docker.com/compose/install/). 2. Check your Docker service: Some users have reported similar issues due to Docker service problems. Try restarting your Docker service and see if that resolves the issue. 3. Check your Docker resources: Ensure that Docker has enough resources (CPU, Memory, Disk Space). You can check and adjust these in your Docker settings. 4. Check your network settings: Ensure that your host machine can resolve the address 'db', which is used by the Airbyte Temporal service to connect to the database. 5. Re-run the upgrade commands: Try to re-run the upgrade commands as mentioned in the [upgrade guide](https://docs.airbyte.com/operator-guides/upgrading-airbyte/). Make sure to pull the latest version of Airbyte from the GitHub repo or download the latest

docker-compose.yaml

and

.env

files. If the issue persists, it would be helpful to have more detailed logs to understand the exact cause of the problem. You can obtain these by running

docker compose logs > logs.txt

and examining the

logs.txt

file. Please note that these suggestions are based on the information available in the provided extracts and may not cover all possible causes of your issue. If the problem continues, I would recommend reaching out to the Airbyte community on their [forum](https://discuss.airbyte.io/) or [Slack](https://airbytehq.slack.com/) for more specific assistance.

@Kevin ND, There was a bug in the Helm chart - that sounds like this - that was fixed two days ago. If you are using Kubernetes/Helm then please make sure you have the latest one. (valeus.yaml file has changed for temporal)