mirror of
https://github.com/langgenius/dify-plugin-daemon.git
synced 2026-07-21 17:25:23 -04:00
plugin start failed #217
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 @shuxnhs on GitHub (Dec 16, 2025).
Self Checks
To make sure we get to you in time, please check the following :)
Versions
Describe the bug
after upgrade plugin-daemon to version 0.4.1, my plugin can not start
`
2025/12/16 07:33:22 logger.go:22: [ERROR]local runtime start failed: test/test:0.0.7@xxxxxx, error: plugin failed to start:
[type=missing, input_value={}, input_type=dict]
For further information visit https://errors.pydantic.dev/2.11/v/missing
icon
Field required [type=missing, input_value={}, input_type=dict]
For further information visit https://errors.pydantic.dev/2.11/v/missing
label
Field required [type=missing, input_value={}, input_type=dict]
For further information visit https://errors.pydantic.dev/2.11/v/missing
created_at
Field required [type=missing, input_value={}, input_type=dict]
For further information visit https://errors.pydantic.dev/2.11/v/missing
resource
Field required [type=missing, input_value={}, input_type=dict]
For further information visit https://errors.pydantic.dev/2.11/v/missing
plugins
Field required [type=missing, input_value={}, input_type=dict]
For further information visit https://errors.pydantic.dev/2.11/v/missing
meta
Field required [type=missing, input_value={}, input_type=dict]
For further information visit https://errors.pydantic.dev/2.11/v/missing`
the manifest.yaml is exist in /app/storage/cwd/xxxxxxx
@dosubot[bot] commented on GitHub (Dec 16, 2025):
Your plugin is failing to start because dify-plugin-daemon v0.4.1 now strictly requires several fields in manifest.yaml that may have been optional or missing in previous versions. The required fields are:
icon(string, max 128 chars),label(I18nObject),description(I18nObject),created_at(timestamp),resource(object, must include at leastmemory),plugins(object), andmeta(object, must includeversion,arch, andrunner). If any of these are missing or incorrectly formatted, you'll get Pydantic validation errors and the plugin won't start.Here's a minimal example of what your manifest.yaml should include for v0.4.1 compatibility:
Make sure to fill in the actual values and add any additional required subfields for
pluginsandmetaas needed. For more details on the schema and validation logic, see the PluginDeclaration struct and validation rules.Updating your manifest.yaml to include all these required fields should resolve the startup failure.
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
@shuxnhs commented on GitHub (Dec 16, 2025):
@dosu.this is my manifest.yaml
version: 0.0.7
type: plugin
author: "test"
name: "test"
description:
en_US: xxxxxxx
zh_Hans: xxxxxx
label:
en_US: "xxxxx"
created_at: "2025-09-02T19:53:50.29298939-04:00"
icon: icon_s_en.svg
resource:
memory: 268435456
permission:
model:
enabled: false
plugins:
models:
- provider/xxx.yaml
meta:
version: 0.0.1
arch:
- amd64
- arm64
runner:
language: python
version: "3.12"
entrypoint: main
@shuxnhs commented on GitHub (Dec 16, 2025):
@dosu i run 'python -m main' on my machine, it run success
{"event": "log", "data": {"level": "INFO", "message": "Installed model: xxxx", "timestamp": 1765874328.916999}}
{"event":"heartbeat","session_id":null,"data":{}}
{"event":"heartbeat","session_id":null,"data":{}}
@dosubot[bot] commented on GitHub (Dec 16, 2025):
Running your plugin with
python -m mainonly checks if your Python code works—it doesn't validate your manifest.yaml. dify-plugin-daemon v0.4.1 enforces strict manifest.yaml schema validation before starting the plugin, which is why you see errors about missing fields likeicon,label,created_at,resource,plugins, andmetaeven though your code runs locally.Looking at your manifest.yaml, here are some things to check and fix:
authorandnamefields must be lowercase, alphanumeric, and can include underscores or dashes (e.g.,author: your_github_id,name: your_plugin_name)."test"is fine if it matches the regex, but make sure it's lowercase.iconfield should be a string (max 128 chars) and ideally a URL or a valid path to an icon file in your package.created_atfield must be in RFC3339 format (e.g.,"2025-09-02T19:53:50Z").resourcefield must includememory(int, required). If you usepermission.storage.size, it must be at least 1024.pluginsfield must include at least one of:tools,models,endpoints,agent_strategies,datasources, ortriggers, each as a list of strings (paths to yaml files that exist in your package).metafield must includeversion(version format),arch(list, e.g.,[amd64, arm64]), andrunner(withlanguage,version,entrypoint).Here's a corrected example based on your manifest:
Make sure all referenced files (like
icon_s_en.svgandprovider/xxx.yaml) exist in your package. If you still get errors, check the error message for the specific field and format. For more details, see the schema definition and the validation logic.If you update your manifest and still see errors, please share the new error message for further help.
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
@shuxnhs commented on GitHub (Dec 16, 2025):
@dosu
i use your corrected example, it also start failed
@dosubot[bot] commented on GitHub (Dec 16, 2025):
Your manifest.yaml content looks correct, so the persistent "Field required" errors almost certainly mean the daemon is not reading or parsing the file you expect. This usually happens if the plugin daemon is looking in the wrong directory, the file is empty/corrupted, or there’s a mismatch in Docker volume mounts or environment variables.
Here’s what to check next:
Make sure your Docker/container volume mounts and environment variables are aligned. The daemon expects to find plugins under a path like
/app/storage/cwd/<plugin-folder>/manifest.yamlby default. Double-check that PLUGIN_STORAGE_LOCAL_ROOT, PLUGIN_WORKING_PATH, and PLUGIN_INSTALLED_PATH are set correctly and that your plugin folder is actually mounted inside the container at the expected location. If these are misaligned, the daemon will read an empty or wrong manifest file, causing all fields to be "missing" even if the file exists on disk (source).Confirm the manifest.yaml is not empty or corrupted inside the running container. Enter the container and run
cat /app/storage/cwd/<your-plugin-folder>/manifest.yamlto verify the file content matches what you expect.Check file permissions: the manifest.yaml must be readable by the user running the daemon process.
Run a YAML linter on your manifest.yaml to catch any invisible formatting or encoding issues (like tabs, BOM, or non-UTF8 encoding).
If you have a working plugin from the official marketplace, try copying its manifest.yaml into your plugin folder as a test. If it still fails, the issue is almost certainly with the environment or path configuration, not the manifest content.
If you share your relevant environment variable values and Docker compose volume mounts, I can help you spot any misconfigurations. This kind of error is almost always a path or mounting issue, not a manifest.yaml content problem (source).
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
@shuxnhs commented on GitHub (Dec 16, 2025):
@dosu other plugins can run success, only this one start failed, i check manifest.yaml
@dosubot[bot] commented on GitHub (Dec 16, 2025):
Since other plugins work and only this one fails—with the error showing all required fields as missing—it's very likely the manifest.yaml for your 'test' plugin is malformed, truncated, or has encoding issues, even if it looks fine in your editor. The daemon treats any malformed, empty, or non-UTF-8 manifest as an empty object, which triggers these "Field required" errors for every required field (source).
Here’s what to do next:
file manifest.yamlandcat -A manifest.yamlinside the failing plugin directory and compare the output to a working plugin. This will reveal encoding issues, BOMs, or invisible characters.yamllint) on the failing manifest.yaml to catch syntax or formatting errors.If the issue persists after these checks, try recreating the manifest.yaml from scratch in a plain text editor set to UTF-8 (no BOM). The file size difference (442 bytes vs 1.1K) also suggests your manifest might be truncated or missing content compared to the working one.
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
@shuxnhs commented on GitHub (Dec 16, 2025):
if the manifest.yaml required fields is missing, it will failed to package plugin ,like: [ERROR]failed to package plugin: Key: 'PluginDeclaration.PluginDeclarationWithoutAdvancedFields.Label.xxxxx' Error:Field validation for 'xxxx' failed on the 'required' tag , but i can package the plugin success@dosu
@Yeuoly commented on GitHub (Dec 17, 2025):
I'd like to have your manifest.yaml and see where the problem is, would you mind provide it?