Hello, I depoly through the CLI (v2.0.2) but the build failed
This is the result log
What are the logs from the build failure?
log is in the attached file
Here is the openruntimes-executor's log
I meant the function's build logs. Click on the 3 dots on your failed deployment, the 3 dots on the far right > Logs.
Also, does the manual deploy work?
The log is log_result.txt
No, it doesnt work!
Heyy 👋 Original message was becasue new images of v3 runtimes were not pulled yet. that resolves automatically after some minutes.
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
Okay, I restarted Appwrite then i click on redeploy from console?
I clicked on redeploy but it doesn’t work
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 #
I solved the issue... is a bug related to proxmox with lxc containers
[SOLVED] Appwrite 1.4.2: Function deployment build failed
what was the fix?
Appwrite works fine, there is no fix but a workaround on Proxmox described here https://forum.proxmox.com/threads/docker-failed-to-register-layer-applylayer-exit-status-1-stdout-stderr-unlinkat-var-log-apt-invalid-argument.119954/
Recommended threads
- Excessive usage of cloud functions is sl...
I have made almost all my requests through cloud functions and jwt , due to security fears of a user editing a field he is not supposed to . This unfortunately...
- Dart Runtime as Function is missing
Hey guys, I set the _APP_FUNCTIONS_RUNTIMES to dart-3.10 and redeployed the appwrite stack but unfortunately the dart runtime doesnt show up. I copied the val...
- Go 1.25 runtime
So I'm trying to use go 1.25 for my functions and I can only find go-1.23 as a function runtime. So I did some searching and found https://github.com/appwrite/a...