🐛 Bug Report: Executor does not start after reboot

[istornz]

👟 Reproduction steps

• Install a fresh version of Appwrite 1.4.4 on a Ubuntu server (don't tested on another os)
• Deploy a function (it works perfectly)
• Reboot the server sudo reboot for exemple
• Trying to execute/deploy function throw an error Could not resolve host: appwrite-executor with status code 0\nError Code: 0

docker compose up -d after each reboot seems to fix the issue (temporary after a reboot)

👍 Expected behavior

Functions should deploy/execute

👎 Actual Behavior

Functions throw an error Could not resolve host: appwrite-executor with status code 0\nError Code: 0

🎲 Appwrite version

Version 1.4.x

💻 Operating system

Linux

🧱 Your Environment

I use Hetzner

👀 Have you spent some time to check if this issue has been raised before?

• I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct

[JoshiJoshiJoshi]

I thought I messed up some configuration over time and that's why it happened, I'm encountering the issue as well and I'm also using Hetzner. Hetzner Cloud ARM Architecture to be more specific.

[stnguyen90]

@JoshiJoshiJoshi to make sure the openruntimes-executor restarts after a reboot, make sure to include restart: unless-stopped in the docker-compose.yml file just like the other services.

[JoshiJoshiJoshi]

@JoshiJoshiJoshi to make sure the openruntimes-executor restarts after a reboot, make sure to include restart: unless-stopped in the docker-compose.yml file just like the other services.

Thanks, that did indeed solve my issue.