plugin start failed

[shuxnhs]

Self Checks

To make sure we get to you in time, please check the following :)

• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
• "Please do not modify this template :) and fill in all the required fields."

Versions

1. dify-plugin-daemon Version: 0.4.1
2. dify-api Version: 1.10.1

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]

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 least memory), plugins (object), and meta (object, must include version, arch, and runner). 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:

version: "0.0.7"
type: "plugin"
name: "your_plugin_name"
author: "your_github_id"
label:
  en_US: "Your Plugin Label"
description:
  en_US: "Your plugin description"
icon: "https://yourdomain.com/icon.png"
created_at: "2025-12-16T07:33:22Z"
resource:
  memory: 128
plugins:
  # Fill in your plugin extensions here
meta:
  version: "0.0.7"
  arch: ["amd64"]
  runner: "python"

Make sure to fill in the actual values and add any additional required subfields for plugins and meta as 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]

@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]

@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]

Running your plugin with python -m main only 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 like icon, label, created_at, resource, plugins, and meta even though your code runs locally.

Looking at your manifest.yaml, here are some things to check and fix:

• The author and name fields 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.
• The icon field should be a string (max 128 chars) and ideally a URL or a valid path to an icon file in your package.
• The created_at field must be in RFC3339 format (e.g., "2025-09-02T19:53:50Z").
• The resource field must include memory (int, required). If you use permission.storage.size, it must be at least 1024.
• The plugins field must include at least one of: tools, models, endpoints, agent_strategies, datasources, or triggers, each as a list of strings (paths to yaml files that exist in your package).
• The meta field must include version (version format), arch (list, e.g., [amd64, arm64]), and runner (with language, version, entrypoint).

Here's a corrected example based on your manifest:

version: "0.0.7"
type: "plugin"
author: "test"
name: "test"
label:
  en_US: "xxxxx"
description:
  en_US: "xxxxxxx"
  zh_Hans: "xxxxxx"
icon: "icon_s_en.svg"
created_at: "2025-09-02T19:53:50Z"
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

Make sure all referenced files (like icon_s_en.svg and provider/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]

@dosu

i use your corrected example, it also start failed

2025/12/16 09:07:48 logger.go:22: [ERROR]local runtime start failed: test/test:0.0.7@e1a07b73318e66f8499e5f126897279299bd475840310bdecfc1501f98e2aee1, 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

root:/app/storage/cwd/test# ls test-0.0.7\@e1a07b73318e66f8499e5f126897279299bd475840310bdecfc1501f98e2aee1/
README.md    _assets  manifest.yaml  provider        requirements.txt   test_metric.py
__pycache__  main.py  models         pyproject.toml  test_embedding.py  test_rerank.py


root:/app/storage/cwd/test# cat test-0.0.7\@e1a07b73318e66f8499e5f126897279299bd475840310bdecfc1501f98e2aee1/manifest.yaml 
version: "0.0.7"
type: "plugin"
author: "test"
name: "test"
label:
  en_US: "xxxxx"
description:
  en_US: "xxxxxxx"
  zh_Hans: "xxxxxx"
icon: "icon_s_en.svg"
created_at: "2025-09-02T19:53:50Z"
resource:
  memory: 268435456
  permission:
    model:
      enabled: false
plugins:
  models:
    - provider/trag.yaml
meta:
  version: "0.0.1"
  arch:
    - amd64
    - arm64
  runner:
    language: python
    version: "3.12"
    entrypoint: main

[dosubot]

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:

1. 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.yaml by 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).

2. 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.yaml to verify the file content matches what you expect.

3. Check file permissions: the manifest.yaml must be readable by the user running the daemon process.

4. Run a YAML linter on your manifest.yaml to catch any invisible formatting or encoding issues (like tabs, BOM, or non-UTF8 encoding).

5. 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]

@dosu other plugins can run success, only this one start failed, i check manifest.yaml

root@dify-plugin-daemon-new-dify-5995b94c47-m5scb:/app/storage/cwd# ls -hl /app/storage/cwd/anspire/anspire_search-0.0.9\@a59824e9507c05c81d582cc5d8384197215d91bf5c787150d8aad723eb5d1a69/
total 28K
-rw-r--r-- 1 root root 6.9K Dec 16 08:45 GUIDE.md
-rw-r--r-- 1 root root 1.8K Dec 16 08:45 PRIVACY.md
-rw-r--r-- 1 root root 3.0K Dec 16 08:45 README.md
drwxr-xr-x 2 root root   34 Dec 16 08:45 __pycache__
drwxr-xr-x 2 root root   59 Dec 16 08:45 _assets
-rw-r--r-- 1 root root  148 Dec 16 08:45 main.py
-rw-r--r-- 1 root root 1.1K Dec 16 08:45 manifest.yaml
drwxr-xr-x 3 root root   77 Dec 16 08:45 provider
-rw-r--r-- 1 root root   82 Dec 16 08:45 requirements.txt
drwxr-xr-x 3 root root  201 Dec 16 08:45 tools
drwxr-xr-x 3 root root   44 Dec 16 08:45 utils

root@dify-plugin-daemon-new-dify-5995b94c47-m5scb:/app/storage/cwd# ls -hl /app/storage/cwd/test/test-0.0.7\@e1a07b73318e66f8499e5f126897279299bd475840310bdecfc1501f98e2aee1/
total 32K
-rw-r--r-- 1 root root  282 Dec 16 09:06 README.md
drwxr-xr-x 2 root root  142 Dec 16 09:07 __pycache__
drwxr-xr-x 2 root root   48 Dec 16 09:06 _assets
-rw-r--r-- 1 root root  125 Dec 16 09:06 main.py
-rw-r--r-- 1 root root  442 Dec 16 09:06 manifest.yaml
drwxr-xr-x 5 root root   56 Dec 16 09:06 models
drwxr-xr-x 3 root root   57 Dec 16 09:06 provider
-rw-r--r-- 1 root root  784 Dec 16 09:06 pyproject.toml
-rw-r--r-- 1 root root 3.3K Dec 16 09:06 requirements.txt

[dosubot]

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:

1. Run file manifest.yaml and cat -A manifest.yaml inside the failing plugin directory and compare the output to a working plugin. This will reveal encoding issues, BOMs, or invisible characters.
2. Run a YAML linter (like yamllint) on the failing manifest.yaml to catch syntax or formatting errors.
3. If you have a working manifest.yaml, try copying it to the failing plugin directory, then overwrite its content line-by-line (not copy-paste) with your intended manifest. This helps rule out hidden encoding or formatting problems.
4. Check for differences in line endings (LF vs CRLF) and indentation (spaces vs tabs).

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]

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]

I'd like to have your manifest.yaml and see where the problem is, would you mind provide it?