Error deploying function from github

When deploying a function from github, it will fail and show a "File Not Found" in the logs. If I look into the logs of the openruntimes-executor container, I see the following:

` [Error] Type: Exception [Error] Message: File Not Found [Error] File: /usr/local/app/http.php [Error] Line: 605 [Error] Type: Exception [Error] Message: Runtime not ready. Error Msg: []

Error: No such container: executor-proj-ibb-64f370a480571e5c9fd0

[Error] File: /usr/local/app/http.php [Error] Line: 319 `

Tested with deno-1.35 and node-20

If I deploy the function manually, it will build as expected.

Btw, it's best to use 3 back ticks with multi-line code. See https://www.markdownguide.org/extended-syntax/#syntax-highlighting

Can you share more of the logs please?

Did you deploy a starter template?

no

here's the repo I am using

https://github.com/ssa-web-solutions/test

just your sample code for deno

it's actually all the log I've

and here's the file I used to deploy manually

would you please try installing one of the starter templates?

I'm unfortunately experiencing the same (File not found) error, with GitHub integration.

Here's the steps I take:

1. I've created a brand new Digital Ocean droplet, pre-installed with Docker.
2. I've installed Appwrite 1.4.1 according to the self hosting documentation
3. I've connected GitHub and Appwrite
4. I can create a function and select one of the starter templates
5. I select the Node.js starter
6. Name: starter function
7. Runtime: Node.js 18
8. Skip the optional variables
9. Create a new repository
10. Select my organization
11. Appwrite creates the starter repo
12. Repo is created
13. Production branch main
14. Root directory is empty
15. Silent mode is left unchecked
16. Create the repo (Appwrite does this for you - this shows in the Functions dashboard after step 17)
17. Appwrite redirects to the Functions page, Building status is shown
18. Appwrite updates the status, Failed is shown
19. Looking into the logs, it shows File not found
20. docker logs appwrite shows no relevant errors

Relevant part of my .env looks like this:

_APP_FUNCTIONS_SIZE_LIMIT=30000000
_APP_FUNCTIONS_TIMEOUT=900
_APP_FUNCTIONS_BUILD_TIMEOUT=900
_APP_FUNCTIONS_CONTAINERS=10
_APP_FUNCTIONS_CPUS=0
_APP_FUNCTIONS_MEMORY=0
_APP_FUNCTIONS_MEMORY_SWAP=0
_APP_FUNCTIONS_RUNTIMES=node-18.0
_APP_EXECUTOR_SECRET=***
_APP_EXECUTOR_HOST=http://executor/v1
_APP_EXECUTOR_RUNTIME_NETWORK=runtimes
_APP_FUNCTIONS_ENVS=node-18.0
_APP_FUNCTIONS_INACTIVE_THRESHOLD=60
OPEN_RUNTIMES_NETWORK=runtimes
_APP_FUNCTIONS_RUNTIMES_NETWORK=runtimes
_APP_FUNCTIONS_MAINTENANCE_INTERVAL=60

This is on a brand new 1.4.1 installation, self-hosted on Digital Ocean, Ubuntu 22.04.

Not sure if related, but when I visit the function settings it shows an empty select field for Runtime.

Notes:

• Creating the function with the Appwrite CLI works, but only when it's a new function.
• If the function already exists and gets updated, I get the Error Param "runtime" is not optional. error.

step 16 Create the repo...you did that yourself?

Nope, it's done by Appwrite, after GitHub integration. Updated the steps above to reflect it's with the GitHub integration

Anything in the executor or the worker builds container logs?

were you able to init a function using cli v3? That version does not work with me. If I use v2, I will get a similar error you got when trying to deploy the function.

Not possible. The quick start boxes never load. If I hit "All templates" -> "Starter function", the "Runtime" select field will be empty, but if I look into th network tab I see it made a request to the server and received the runtimes I have set in the .env files.

@Lucas Reis : Check https://discord.com/channels/564160730845151244/1147460737065820210 for the file not found error. There are 2 missing volumes you need to add to your docker-compose

@Lucas Reis : and you need to set all Quickstart Runtimes for the Loading Spinners to disappear: _APP_FUNCTIONS_RUNTIMES=node-18.0,php-8.0,python-3.9,ruby-3.0,dart-2.17

awesome, it worked, thank you so much @QuadWord 🙂

interesting why its not by default in the yml file?

I guess they just overlooked it in the first release. Similar to the _APP_EXECUTOR_HOST=http://executor/v1 name, which needed to be updated. Such things happen if you release a major version. I guess they will fix this with the next patch-release. If you have a productive environment i can only recommend not to install major releases in the first week after release.

yeah i'm gonna return from vacation in 2 weeks and hopefully the version will be bumped up and i will try again to get things up and running