Back

Functions not deploying now, tar: can't open 'tmp/....

  • 0
  • Functions
TernaryBash
19 Apr, 2023, 03:46

Migrated from 1.2.1 (Mac) -> 1.3 (Linux) for staging. Cannot deploy function now which was working on Mac. I am using docker desktop on Linux and I have the /tmp directory mounted. Anyone else experiencing this issue or know how to triage? Function: Nodejs, and I do not have SSL since this is on local. Logs: [Error] Method: PATCH [Error] URL: /v1/functions/:functionId/deployments/:deploymentId [Error] Type: Appwrite\Extend\Exception [Error] Message: Build with the requested ID is building and not ready for execution. [Error] File: /usr/src/code/app/controllers/api/functions.php [Error] Line: 531 [Error] Timestamp: 2023-04-19T03:22:30+00:00 [Error] Method: PATCH [Error] URL: /v1/functions/:functionId/deployments/:deploymentId [Error] Type: Appwrite\Extend\Exception [Error] Message: Build with the requested ID is building and not ready for execution. [Error] File: /usr/src/code/app/controllers/api/functions.php [Error] Line: 531 [Error] Timestamp: 2023-04-19T03:31:49+00:00 [Error] Method: PATCH [Error] URL: /v1/functions/:functionId/deployments/:deploymentId [Error] Type: Appwrite\Extend\Exception [Error] Message: Build with the requested ID is building and not ready for execution. [Error] File: /usr/src/code/app/controllers/api/functions.php [Error] Line: 531

TL;DR
Functions are not deploying and an error message is being displayed: "Build with the requested ID is building and not ready for execution." The issue may be related to the /tmp directory being mounted. It could also be a result of migrating from 1.2.1 (Mac) to 1.3 (Linux) for staging. The user suggests restarting the services and checking if any containers are running using `docker compose ps`. There is no SSL involved as it is a local deployment. The problem seems to be resolved after restarting the services, but the user plans to test it again later.
Drake
19 Apr, 2023, 03:47

What are the build logs for the new deployment?

TernaryBash
19 Apr, 2023, 03:48

Is that the "Logs" tab when selected while looking at the deployment view?

Drake
19 Apr, 2023, 03:49

I think so

TernaryBash
19 Apr, 2023, 03:50

"No logs recorded". Also build time is 0ms so I don't think it every tried? 🤷‍♂️

Drake
19 Apr, 2023, 03:54

Try running docker compose ps to check if all containers are running. Then, check the worker builds container logs

TernaryBash
19 Apr, 2023, 03:58

They were. 🤔 sooooooo I said w/e and restarted the services and now they work. Since i'm working on automation I wonder if something is needed in-between the creating of the setup when dealing with the filesystem. Thanks Steven. I'm going to be booting another instance again later this week. I'll see if this happens again. Could have been the mounts 🤷‍♂️ [SOLVED/ish]

Drake
19 Apr, 2023, 03:59

Maybe...I've seen all sorts of weird behavior with docker desktop, especially on Linux

TernaryBash
19 Apr, 2023, 03:59

Ahhh, good to know. I'll keep that in mind going forward. Thank you.

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