dify - 💡(How to fix) Fix [Refactor/Chore] Upgrade plugin daemon image for improved runtime stability [1 pull requests]

Self Checks

• I have read the Contributing Guide and Language Policy.
• This is only for refactors or chores; if you would like to ask a question, please head to Discussions.
• I have searched for existing issues, including closed ones.
• I confirm that I am using English to submit this report, otherwise it will be closed.
• Please do not modify this template :) and fill in all the required fields.

Description

Dify's Docker deployment depends on langgenius/dify-plugin-daemon for plugin lifecycle management, local plugin execution, remote debugging, and plugin invocation routing.

We should upgrade or refresh the bundled plugin daemon image to the latest compatible stable release and verify that the Docker deployment files stay consistent across:

• docker/docker-compose.yaml
• docker/docker-compose-template.yaml
• docker/docker-compose.middleware.yaml

Current main pins langgenius/dify-plugin-daemon:0.6.0-local. Upstream currently lists 0.6.0 as the latest release, with a stability fix for the daemon running as PID 1: https://github.com/langgenius/dify-plugin-daemon/releases/tag/0.6.0

Proposed scope:

• Confirm the latest compatible dify-plugin-daemon image tag for this Dify release line.
• Update all Docker compose references consistently if a newer compatible tag or image variant is available.
• Confirm whether -local is still the correct image variant for bundled Docker deployments.
• Review daemon release notes for breaking changes before updating.
• Add a short release note or upgrade note if operators need to pull the new image explicitly.

Acceptance criteria:

• All Docker compose plugin daemon image tags are consistent.
• The selected daemon version is compatible with the current Dify API plugin contracts.
• Existing plugin install, list, invoke, and debug flows continue to work in Docker deployment.
• Any operator-facing upgrade caveats are documented.

Motivation

Plugin daemon stability directly affects plugin installation, startup, invocation, remote debugging, and self-hosted deployments. Keeping the daemon image aligned with the latest compatible stable release reduces the risk of container lifecycle issues and avoids users running daemon builds with known stability problems.

Additional Context

The upstream 0.6.0 release notes call out a daemon PID 1 fix, which is relevant to Docker/container lifecycle stability. This issue is intended to track the compatibility check and Docker image alignment work for the 1.14.2 milestone.