I'm sorry to hear that you're encountering issues with your Airbyte deployment on GCP. Based on the information provided in the extracts, it seems like there might be a couple of things going wrong. For the

airbyte/airbyte-api-server:0.50.9: exec /bin/bash: exec format error

, it's hard to say without more information. It could be an issue with the Docker image itself or the environment it's running in. For the

airbyte/temporal:0.50.9 : Unable to create dynamic config client. Error: unable to validate dynamic config: dynamic config: config/dynamicconfig/development.yaml: stat config/dynamicconfig/development.yaml: no such file or directory

error, it seems like the application is unable to find a required configuration file. Unfortunately, the extracts provided do not contain specific solutions to these issues. However, the Airbyte community has been very helpful in resolving similar issues in the past. I would recommend reaching out to the Airbyte community on [Slack](https://slack.airbyte.com/) for further assistance. You can also check the [Troubleshooting section](https://docs.airbyte.com/deploying-airbyte/on-gcp-compute-engine) of the Airbyte documentation for general guidance on resolving issues with your Airbyte deployment. I hope this helps, and I wish you the best of luck with your Airbyte deployment!

basically make sure all files ownership is the user running the commands, also create an empty file as described in the link.