🐛 Bug Report: Could not resolve host

[kempsu]

👟 Reproduction steps

I initialize a new function (nodejs 16.0) using the Appwrite CLI and set up the example function project using the correct credentials (project id, api key, etc.)

If I deploy the function to my local appwrite instance (running via docker) it works just fine. The execution of the function is done without custom data using the web frontend of my appwrite instance.

If I try to do the same on my server (Ubuntu 22.04, Appwrite also running via docker. Setup is as identical as it can be) it does not work.

👍 Expected behavior

I would expect the function to run just fine also on a docker-instance on some virtual server.

👎 Actual Behavior

The function crashes after a couple of seconds, this is the error message:

An internal curl error has occurred within the executor! Error Msg: Could not resolve host: 63b09b04167263769ffe-63b09c5c9281f34c2f3b

Output of sudo docker logs appwrite-executor -f:

Warming up Node.js 16.0 environment...
Warming up PHP 8.0 environment...
Warming up Ruby 3.0 environment...
Warming up Python 3.9 environment...
Removing orphan runtimes...
Successfully Warmed up Ruby 3.0!
Successfully Warmed up PHP 8.0!
Successfully Warmed up Python 3.9!
Successfully Warmed up Node.js 16.0!
Building container : 63b09b04167263769ffe-63b09c5c9281f34c2f3b
Build Stage completed in 0 seconds
Executing Runtime: 63b09b04167263769ffe-63b09c5c9281f34c2f3b
[Error] Type: Exception
[Error] Message: An internal curl error has occurred within the executor! Error Msg: Could not resolve host: 63b09b04167263769ffe-63b09c5c9281f34c2f3b
[Error] File: /usr/src/code/app/executor.php
[Error] Line: 544

🎲 Appwrite version

Version 1.2.x

💻 Operating system

Linux

🧱 Your Environment

Appwrite 1.2.0, Ubuntu 22.04 LTS, latest docker environment with docker compose.

👀 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

[stnguyen90]

@kempsu thanks for raising this issue! 🙏🏼 Would you please take a look at #4671 (comment) and see if that resolves your problem?

[kempsu]

@stnguyen90 thanks for taking the time to point me towards this comment. It is indeed correct, it is the same issue and I was not aware of it. My apologies! Also Happy New Year! :)