Unverified50% confidenceSolutionExact time
In self-hosted deployments, Dify's base URL can use a container alias (such as http://dify:5001/v1), provided that the LangBot plugin container and the Dify container are on the same Docker network.
1
Sources
50%
Confidence
Long-term
Relevance
10/19/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedDify 的 Agent 工具运行在容器内部，容器的 localhost 指向容器自身网络栈，无法直接通过 localhost 访问宿主机数据库服务，是数据库连接失败的根源67% similarUnverified由于Docker默认创建的bridge网络允许容器间及容器与宿主机自由通信，Dify容器可与本机MySQL或VMware虚拟机内环境正常通信66% similarUnverifiedWhen Dify is started via Docker Compose it creates an independent bridge network, and localhost inside a container points to the container itself; when MySQL is installed on the Windows host, the Dify container needs to use host.docker.internal rather than 127.0.0.1 to access the host.65% similarVerifiedMisconfigured container runtimes (such as the Docker daemon) can be exploited to achieve container escape and gain host machine privileges.63% similarUnverifiedContainers within the same Docker Compose network can access each other using the container name as the hostname, so when n8n connects to Postgres, the Host field can be filled in directly with the container name postgres.63% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1066152API
curl https://kongchang.com/api/v1/knowledge/claims/1066152MCP
get_claim(id=1066152)