mirror of
https://github.com/langgenius/dify-plugin-daemon.git
synced 2026-07-21 17:25:23 -04:00
Failed to pre-compile the plugin: ./.venv/lib/python3.12 #52
Reference in New Issue
Block a user
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?
Originally created by @DavideDelbianco on GitHub (Mar 21, 2025).
When you self host the plugin daemon and have 2+ instances, when installing a new plugin you will get the error: failed to pre-compile the plugin: ./.venv/lib/python3.12
This happens especially in K8S installations that probably used the helm chart that creates a WriteMany volume.
Having multiple daemons attempting to install the plugin on a shared disc at the same time causes issues.
I've resolved hosting plugins and persistence in S3 with v0.0.6 and this allowed me to let every instance have its own volume and not a shared one.
You should probably implement some kind of red-lock mechanism to allow just one instance to write on the disk at any given time or document the S3 alternative with NOT shared volumes
This is probably something that you never experience when developing locally using just a single instance with docker-compose
@Yeuoly commented on GitHub (Mar 28, 2025):
Dify plugin daemon dose not support multiple instances official now, you can concat us if you are interested in our enterprise edition, we support k8s deployment
@DavideDelbianco commented on GitHub (Mar 29, 2025):
Oh I see, not using it online, but in a raspberry with k3s and by default I set every deployment manifest with a count of 2. Since you probably have to scale it with the cloud version I thought it would support scaling, my bad
@Yeuoly commented on GitHub (Mar 30, 2025):
Thanks for you understanding : )