mirror of
https://github.com/langgenius/dify-plugin-daemon.git
synced 2026-07-21 17:25:23 -04:00
add ollama model ,bug error #241
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 @ufgufg on GitHub (Feb 4, 2026).
Self Checks
To make sure we get to you in time, please check the following :)
Versions
Describe the bug
error="copy plugin to working directory error: open _assets\icon_l_en.svg: file does not exist\nopen _assets\icon_l_en.svg: file does not exist\nextract plugin to working directory error\nextract plugin to working path error\nfailed to init environment
the _assets is not ,only have assets,and the svg filename is not icon_I_en
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
@dosubot[bot] commented on GitHub (Feb 4, 2026):
Hi @ufgufg! I'm Dosu and I’m helping the dify-plugin-daemon team.
The error happens because dify-plugin-daemon expects all plugin asset files (like SVG icons) to be in a directory named
_assets, notassets, and the filenames must match exactly what’s declared in yourmanifest.yaml. For Ollama and similar plugins, the expected icon filenames are usuallyicon.svgandicon-dark.svg(or locale-specific variants). If the manifest references a file likeicon_l_en.svg, that file must exist in_assets—otherwise, initialization fails with a file not found error. This is strictly enforced by the asset validation logic in the daemon, and any mismatch in directory name or filename will cause errors during plugin extraction and setup (source, source).To fix this: rename your
assetsdirectory to_assets, make sure the SVG icon files are named exactly as referenced in yourmanifest.yaml, and update the manifest if needed. On Windows, make sure you use forward slashes (/) in paths, as backslashes can cause issues (source). If you still see errors after making these changes, let me know what you’ve tried so far or share more details.To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
@ufgufg commented on GitHub (Feb 4, 2026):
thankyou,i dont know how to edit
@dosubot[bot] commented on GitHub (Feb 4, 2026):
The error happens because dify-plugin-daemon only looks for icon files in a folder named
_assets, and the filenames must match exactly what is written in yourmanifest.yamlfile (for example,icon_l_en.svg)—not the long hashed names you see now. Here’s how you can fix it on Windows:storage/assetsfolder, but the actual plugin’s folder—usually insidepluginorplugin_packages).assets, right-click it, choose “Rename”, and change it to_assets._assetsfolder. Make sure the SVG icon files inside are named exactly as listed in yourmanifest.yaml(for example,icon_l_en.svg). If not, right-click each file and choose “Rename” to match the correct name.manifest.yaml(you can use Notepad or any text editor), and look for lines likeicon: icon_l_en.svg. That’s the name your SVG file must have._assetsfolder with the right names.The files with long hashed names in your screenshot are not correct—they must match the names in
manifest.yamlexactly, or the plugin won’t start source source.If you need step-by-step help finding your plugin folder or editing
manifest.yaml, let me know!To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
@ufgufg commented on GitHub (Feb 4, 2026):
I installed the Ollama model from the Dify model provider, but there is no manifest.yaml file as you mentioned, nor have I found the _assets folder. Could you please take a look
@dosubot[bot] commented on GitHub (Feb 4, 2026):
You don't need to worry about manifest.yaml or the _assets folder when adding Ollama as a model provider in Dify—those files and folders are only required for custom plugins, not for provider-based models like Ollama, Azure, or Cohere. The provider integration is handled internally by Dify, so you won't see or need to manage those files yourself. If you're not seeing any errors after adding Ollama as a provider, everything is working as expected — no manual asset management is needed source.
If you do run into errors after adding Ollama, the most common cause is missing dependencies (like numpy) in the plugin-daemon container, not missing manifest.yaml or _assets. If you see a specific error, let me know the details and I can help troubleshoot source.
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
@ufgufg commented on GitHub (Feb 4, 2026):
@dosubot add ollama
@ufgufg commented on GitHub (Feb 4, 2026):
@dosubot this firest wrong
@dosubot[bot] commented on GitHub (Feb 4, 2026):
The error is happening because the Ollama plugin package is missing a required SVG icon file named
_assets/icon_l_en.svg. The plugin system checks for this exact file during installation, and if it’s not present, initialization fails — this is a strict requirement enforced by the code, not a user mistake (source, source).To fix it:
pluginorplugin_packages)._assetsif it doesn’t exist.icon_l_en.svgto_assets. You can use any SVG image as a placeholder if you don’t have the original.manifest.yaml, make sure the icon filename matches what’s referenced there.After you add the missing file, try installing the plugin again. If you need help creating or finding an SVG file, let me know where you got the plugin package and I can suggest a workaround or a generic icon you can use.
This issue is common with some plugin packages and is not caused by your environment or setup (source).
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
@ufgufg commented on GitHub (Feb 4, 2026):
@dosubot
i create _assets and copy .svg file
also wrong,is placeholder wrong?
https://github.com/langgenius/dify-plugin-daemon/issues/595#issuecomment-3845648777
and Adding "ollama" to "dify" should be quite simple, shouldn't it
@dosubot[bot] commented on GitHub (Feb 4, 2026):
The placeholder SVG file itself is not the problem—as long as it’s a valid SVG (even a minimal one), the daemon only checks that the filename matches exactly what’s referenced in manifest.yaml and that it’s present in the
_assetsfolder. It does not check the SVG content, size, or format beyond basic file existence — so a simple SVG like this is enough:If you’re still seeing the same error, double-check that the filename is exactly
icon_l_en.svg(not a typo, not uppercase/lowercase mismatch), and that it’s inside the_assetsfolder—notassets—in your plugin directory. Also, make sure your manifest.yaml references the correct filename and uses forward slashes (/) in paths, especially on Windows, as backslashes can cause issues source.Adding Ollama as a plugin requires the package to include both a manifest.yaml and the correct assets. If you’re adding Ollama as a model provider (not as a plugin), you don’t need to manage these files—the integration is handled internally by Dify source. If you’re trying to install a plugin and the package is missing manifest.yaml or the required assets, it won’t work until those are added and named exactly as expected source.
If the error persists after these checks, there may be invisible formatting or encoding issues in the manifest.yaml or filenames (like BOM, CRLF line endings, or tabs). Let me know the exact error message you see after adding the placeholder, and I can help troubleshoot further.
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
@ufgufg commented on GitHub (Feb 4, 2026):
@dosubot
filename is right,
I am at the dity model supplier's location, and I am encountering an error when installing ollama
@dosubot[bot] commented on GitHub (Feb 4, 2026):
The error happens because the Ollama plugin package you’re installing from the Dify model provider is missing required files inside the package itself—specifically, manifest.yaml and the SVG icon(s) in the _assets folder. The plugin system checks for these files inside the package during installation, not in your local storage folders, so manually creating _assets or copying SVGs outside the package won’t fix it. This is a strict requirement enforced by the asset validation logic, and installation will always fail if the package is incomplete or incorrectly structured — even if the filename is correct or you add a placeholder SVG yourself source.
To resolve this, you’ll need a plugin package that includes both manifest.yaml and the required icons in _assets, as distributed by the plugin author. If the official Ollama package is missing these files, installation cannot succeed until the package is updated upstream. You can check for a newer or corrected Ollama plugin package in the Dify marketplace or on GitHub. If you have access to the plugin zip/tarball, verify its contents before installing: it should contain manifest.yaml and _assets/icon_l_en.svg (and possibly icon-dark.svg) source.
If you see further errors after updating or replacing the package, share the exact error message and I can help interpret the logs.
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other