
Hello, I migrated one of my Appwrite server from 1.3.7 to 1.3.8 and to a new domain.
When trying to call a function, I get an error message saying that the runtime is not activated.
I checked in the .env
, I still have deno-1.24
in the _APP_FUNCTIONS_RUNTIMES
variable.
I tried restarting several times, without luck.
I tried deno-1.21
, not working either.
I tried removing the python-3.9
runtime, and it disappears. So I get the variable name correct.
I did run the docker compose exec migrate
command.
I tried enabling the cpp-17.0
runtime, which works.
With this value:
_APP_FUNCTIONS_RUNTIMES=node-16.0,deno-1.24,cpp-17.0
I get these logs in appwrite-executor
:
Warming up Node.js 16.0 environment...
Warming up C++ 17.0 environment...
Removing orphan runtimes...
Successfully Warmed up Node.js 16.0!
Successfully Warmed up C++ 17.0!
Edit for more context: I have deno-1.24 functions deployed that have an execution history from the previous deployment.
Any idea?

I deleted all my deployed functions, it still does not work.
I would really appreciate some help as my whole production environment is halted because of this bug....

Ok, it seems that the Deno open runtimes is not compatible with ARM, and my new server is ARM-based Not 100% sure it's linked to that
If so, there should be at least some kind of error somewhere to indicate the issue Especially since the doc states that Appwrite is ARM-compatible, and that ARM servers are likely to grow in popularity

Re-deployed on a x86 server, this is working. I'm filling an issue.

Recommended threads
- Server Error when Pushing a Function
Get this ambiguous error when trying to push my function, it's TypeScript using NodeJS 18 ``` ? Which functions would you like to push? get-grades (get-grades)...
- Having errors migrating to cloud
Project will not migrate compeltely
- ENV vars not updating
When i do `nano .env` it shows `_APP_DOMAIN_TARGET=` as set to my domain, but when i do `docker compose exec appwrite vars` it shows `_APP_DOMAIN_TARGET=` as ...
