langgenius/dify-plugin-daemon
1
0
Fork 0
mirror of https://github.com/langgenius/dify-plugin-daemon.git synced 2026-07-21 17:25:23 -04:00
Code Issues 111 Packages Projects Releases 10 Wiki Activity

Are you planning to compatible with Google Cloud? #44

New Issue
Closed
opened 2026-02-16 00:19:19 -05:00 by yindo · 10 comments
yindo commented 2026-02-16 00:19:19 -05:00
Owner
Copy Link
Copy Source

Originally created by @sotazum on GitHub (Mar 18, 2025).

Hi, I appreciate your great effort to build such plugin systems.

I have been developing and operating Google Cloud Terraform repository for self-hosting Dify.

Now we support plugin daemon local mode and use Filestore (NFS) as persistent volumes of plugin storage and working path. But some problems probably because of slower I/O has occurred like below.

https://github.com/DeNA/dify-google-cloud-terraform/issues/17
https://github.com/DeNA/dify-google-cloud-terraform/issues/19

Do you have a load map compatible with Google Cloud in serverless mode in the near future?

I would be happy to discuss Google Cloud support in this thread!

Originally created by @sotazum on GitHub (Mar 18, 2025). Hi, I appreciate your great effort to build such plugin systems. I have been developing and operating Google Cloud Terraform repository for self-hosting Dify. Now we support plugin daemon local mode and use Filestore (NFS) as persistent volumes of plugin storage and working path. But some problems probably because of slower I/O has occurred like below. https://github.com/DeNA/dify-google-cloud-terraform/issues/17 https://github.com/DeNA/dify-google-cloud-terraform/issues/19 Do you have a load map compatible with Google Cloud in serverless mode in the near future? I would be happy to discuss Google Cloud support in this thread!
yindo closed this issue 2026-02-16 00:19:19 -05:00
yindo commented 2026-02-16 00:19:19 -05:00
Author
Owner
Copy Link
Copy Source

@ianishar commented on GitHub (Mar 18, 2025):

is the move from gcs to filestore related to timeout when cloud run R/W to gcs?
so need a filestore that is more persistent related to time?

@ianishar commented on GitHub (Mar 18, 2025): is the move from gcs to filestore related to timeout when cloud run R/W to gcs? so need a filestore that is more persistent related to time?
yindo commented 2026-02-16 00:19:20 -05:00
Author
Owner
Copy Link
Copy Source

@Yeuoly commented on GitHub (Mar 18, 2025):

Hmmm, I guess you need a serverless runtime instead of the persistent solution, but I'm not sure if GoogleCloud supports it like AWSLambda, have you got any idea?

@Yeuoly commented on GitHub (Mar 18, 2025): Hmmm, I guess you need a serverless runtime instead of the persistent solution, but I'm not sure if GoogleCloud supports it like AWSLambda, have you got any idea?
yindo commented 2026-02-16 00:19:20 -05:00
Author
Owner
Copy Link
Copy Source

@sotazum commented on GitHub (Mar 18, 2025):

is the move from gcs to filestore related to timeout when cloud run R/W to gcs?
so need a filestore that is more persistent related to time?

Filestore is faster than GCS FUSE. But Filestore is temporary solution I use in my repo to make container volumes persistent.

If plugin daemon serverless mode officially supports Google Cloud, its resources would be Cloud Run Functions and Cloud Storage.

@sotazum commented on GitHub (Mar 18, 2025): > is the move from gcs to filestore related to timeout when cloud run R/W to gcs? > so need a filestore that is more persistent related to time? Filestore is faster than GCS FUSE. But Filestore is temporary solution I use in my repo to make container volumes persistent. If plugin daemon serverless mode officially supports Google Cloud, its resources would be Cloud Run Functions and Cloud Storage.
yindo commented 2026-02-16 00:19:20 -05:00
Author
Owner
Copy Link
Copy Source

@sotazum commented on GitHub (Mar 18, 2025):

Hmmm, I guess you need a serverless runtime instead of the persistent solution, but I'm not sure if GoogleCloud supports it like AWSLambda, have you got any idea?

Cloud Run Functions would be equivalent to AWS Lambda. Cloud Run Functions can execute Python code by an event trigger like HTTP requests.

@sotazum commented on GitHub (Mar 18, 2025): > Hmmm, I guess you need a serverless runtime instead of the persistent solution, but I'm not sure if GoogleCloud supports it like AWSLambda, have you got any idea? Cloud Run Functions would be equivalent to AWS Lambda. Cloud Run Functions can execute Python code by an event trigger like HTTP requests.
yindo commented 2026-02-16 00:19:20 -05:00
Author
Owner
Copy Link
Copy Source

@ianishar commented on GitHub (Mar 18, 2025):

Filestore is faster than GCS FUSE. But Filestore is temporary solution I use in my repo to make container volumes persistent.

If plugin daemon serverless mode officially supports Google Cloud, its resources would be Cloud Run Functions and Cloud Storage.

i got error like this
init environment failed: failed to create virtual environment: exit status 1, output: Using CPython 3.12.3 interpreter at: /usr/bin/python3
init environment failed: failed to create virtual environment: exit status 1, output: Using CPython 3.12.3 interpreter at: /usr/bin/python3"

Image
init environment failed: failed to start command: fork/exec /app/storage/cwd/ainun/wallex-explore-0.0.1@ed62609c6bf3f62da223b8d46b16d9083e42a28a06dca9ccfd52e999d7a5ce14/.venv/bin/python: no such file or directory, retry in 30s
why it happen?

@ianishar commented on GitHub (Mar 18, 2025): > Filestore is faster than GCS FUSE. But Filestore is temporary solution I use in my repo to make container volumes persistent. > > If plugin daemon serverless mode officially supports Google Cloud, its resources would be Cloud Run Functions and Cloud Storage. i got error like this init environment failed: failed to create virtual environment: exit status 1, output: Using CPython 3.12.3 interpreter at: /usr/bin/python3 init environment failed: failed to create virtual environment: exit status 1, output: Using CPython 3.12.3 interpreter at: /usr/bin/python3" ![Image](https://github.com/user-attachments/assets/555e6aaf-6d63-4a1d-9ee7-ea8de47faa6a) init environment failed: failed to start command: fork/exec /app/storage/cwd/ainun/wallex-explore-0.0.1@ed62609c6bf3f62da223b8d46b16d9083e42a28a06dca9ccfd52e999d7a5ce14/.venv/bin/python: no such file or directory, retry in 30s why it happen?
yindo commented 2026-02-16 00:19:20 -05:00
Author
Owner
Copy Link
Copy Source

@alliecatowo commented on GitHub (Mar 19, 2025):

Second this! Cloud functions has a pretty robust go library as well, it would make the integration pretty smooth.

@alliecatowo commented on GitHub (Mar 19, 2025): Second this! Cloud functions has a pretty robust go library as well, it would make the integration pretty smooth.
yindo commented 2026-02-16 00:19:21 -05:00
Author
Owner
Copy Link
Copy Source

@DavideDelbianco commented on GitHub (Mar 22, 2025):

Filestore is faster than GCS FUSE. But Filestore is temporary solution I use in my repo to make container volumes persistent.
If plugin daemon serverless mode officially supports Google Cloud, its resources would be Cloud Run Functions and Cloud Storage.

i got error like this init environment failed: failed to create virtual environment: exit status 1, output: Using CPython 3.12.3 interpreter at: /usr/bin/python3 init environment failed: failed to create virtual environment: exit status 1, output: Using CPython 3.12.3 interpreter at: /usr/bin/python3"

Image init environment failed: failed to start command: fork/exec /app/storage/cwd/ainun/wallex-explore-0.0.1@ed62609c6bf3f62da223b8d46b16d9083e42a28a06dca9ccfd52e999d7a5ce14/.venv/bin/python: no such file or directory, retry in 30s�[0m why it happen?

Take a look at #132
My WriteMany volume was based on NFS and had the same issue.

@DavideDelbianco commented on GitHub (Mar 22, 2025): > > Filestore is faster than GCS FUSE. But Filestore is temporary solution I use in my repo to make container volumes persistent. > > If plugin daemon serverless mode officially supports Google Cloud, its resources would be Cloud Run Functions and Cloud Storage. > > i got error like this init environment failed: failed to create virtual environment: exit status 1, output: Using CPython 3.12.3 interpreter at: /usr/bin/python3 init environment failed: failed to create virtual environment: exit status 1, output: Using CPython 3.12.3 interpreter at: /usr/bin/python3" > > ![Image](https://github.com/user-attachments/assets/555e6aaf-6d63-4a1d-9ee7-ea8de47faa6a) init environment failed: failed to start command: fork/exec /app/storage/cwd/ainun/wallex-explore-0.0.1@ed62609c6bf3f62da223b8d46b16d9083e42a28a06dca9ccfd52e999d7a5ce14/.venv/bin/python: no such file or directory, retry in 30s�[0m why it happen? Take a look at #132 My WriteMany volume was based on NFS and had the same issue.
yindo commented 2026-02-16 00:19:21 -05:00
Author
Owner
Copy Link
Copy Source

@Yeuoly commented on GitHub (Mar 28, 2025):

We have a more robust and scaleable support in enterprise edition just like AWSLambda, but feel free to make your own one

@Yeuoly commented on GitHub (Mar 28, 2025): We have a more robust and scaleable support in enterprise edition just like AWSLambda, but feel free to make your own one
yindo commented 2026-02-16 00:19:21 -05:00
Author
Owner
Copy Link
Copy Source

@neyec commented on GitHub (Apr 16, 2025):

Hi, turning off throttling in Cloud Run (instance-based billing) helped me solve many of the plugin errors I had; for example, precompiling a plugin went from 30 minutes to a few seconds. Now I'm using the plugin-daemon with Cloud Storage only and it works pretty well.

@neyec commented on GitHub (Apr 16, 2025): Hi, turning off throttling in Cloud Run (instance-based billing) helped me solve many of the plugin errors I had; for example, precompiling a plugin went from 30 minutes to a few seconds. Now I'm using the plugin-daemon with Cloud Storage only and it works pretty well.
yindo commented 2026-02-16 00:19:21 -05:00
Author
Owner
Copy Link
Copy Source

@41tair commented on GitHub (Jun 11, 2025):

We've added the documentation for the SRI (Serverless Runtime Interface). You can check it out here:
👉 https://github.com/langgenius/dify-plugin-daemon/blob/main/docs/runtime/sri.md

@41tair commented on GitHub (Jun 11, 2025): We've added the documentation for the SRI (Serverless Runtime Interface). You can check it out here: 👉 https://github.com/langgenius/dify-plugin-daemon/blob/main/docs/runtime/sri.md
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Windows
bug
cmd
documentation
enhancement
go
good first issue
plugin-daemon
pull-request
Mirrored from GitHub Pull Request
 question
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify-plugin-daemon#44
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?