Back

[SOLVED] Appwrite 1.4.2: Function deployment build failed

  • 0
  • Functions
Roberto_From_Brescia
8 Sep, 2023, 09:27

Hello, I depoly through the CLI (v2.0.2) but the build failed

This is the result log

TL;DR
Appwrite 1.4.2 is experiencing a build failure, specifically related to proxmox with lxc containers. There is a workaround provided in the Proxmox forum. The issue may also be caused by the v3 node runtime not being pulled properly. One user suggests manually pulling the v3-18.0 image in the container but encounters an error. Restarting Appwrite and using the command "docker compose down && docker compose up -d" is recommended to resolve the issue. After some time, the v3 runtimes should be pulled automatically and deployments should work fine. There is also a suggestion to check the
darShan
8 Sep, 2023, 09:35

What are the logs from the build failure?

Roberto_From_Brescia
8 Sep, 2023, 09:37

log is in the attached file

Roberto_From_Brescia
8 Sep, 2023, 09:57

Here is the openruntimes-executor's log

darShan
8 Sep, 2023, 10:16

I meant the function's build logs. Click on the 3 dots on your failed deployment, the 3 dots on the far right > Logs.

darShan
8 Sep, 2023, 10:28

Also, does the manual deploy work?

Roberto_From_Brescia
8 Sep, 2023, 10:35

The log is log_result.txt

Roberto_From_Brescia
8 Sep, 2023, 10:35

No, it doesnt work!

Meldiron
8 Sep, 2023, 10:48

Heyy 👋 Original message was becasue new images of v3 runtimes were not pulled yet. that resolves automatically after some minutes.

Meldiron
8 Sep, 2023, 10:49

After that, runtime might be considered stuck, as startup took more than expected. I would recommend docker compose down && docker compose up -d, to restart appwrite.

Considering some time passed already, you should have the images pulled. Now deployments should work fine

Roberto_From_Brescia
8 Sep, 2023, 10:56

Okay, I restarted Appwrite then i click on redeploy from console?

Roberto_From_Brescia
8 Sep, 2023, 11:08

I clicked on redeploy but it doesn’t work

Roberto_From_Brescia
8 Sep, 2023, 11:58

v3 node runtime not pulled yet... I try pull it manully in the container but have this error

/usr/local # docker image pull openruntimes/node:v3-18.0 v3-18.0: Pulling from openruntimes/node df9b9388f04a: Already exists 4fababc43238: Pull complete ab29cc3c2246: Pull complete 759c4cf4639e: Pull complete 09100208439e: Pull complete 121c3229518a: Pull complete 5479ed20b09d: Pull complete f55095355fae: Pull complete e9594ca838da: Pull complete 4f4fb700ef54: Pull complete 055f650a9cd5: Pull complete a90445306752: Pull complete 96992ee31b60: Extracting [==================================================>] 235.6kB/235.6kB 846260c83587: Download complete 38b057310d21: Download complete ce85934d2d54: Download complete failed to register layer: ApplyLayer exit status 1 stdout: stderr: unlinkat /root/.npm/_cacache/content-v2/sha512/6f/cb: invalid argument /usr/local #

Roberto_From_Brescia
8 Sep, 2023, 13:55

I solved the issue... is a bug related to proxmox with lxc containers

Drake
8 Sep, 2023, 18:18

[SOLVED] Appwrite 1.4.2: Function deployment build failed

Drake
8 Sep, 2023, 18:18

what was the fix?

Roberto_From_Brescia
9 Sep, 2023, 09:25
Reply

Reply to this thread by joining our Discord

Reply on Discord

Need support?

Join our Discord

Get community support by joining our Discord server.

Join Discord

Get premium support

Join Appwrite Pro and get email support from our team.

Learn more