Replies: 7 comments 1 reply
-
same question,When I used Docker deployment to upgrade to version 0.14.1, my “docker-api-1、docker-worker-1”two containers kept restarting. |
Beta Was this translation helpful? Give feedback.
-
me too,This is a system adaptation issue, I've already changed my system |
Beta Was this translation helpful? Give feedback.
-
重启nginx
…---原始邮件---
发件人: "Xiaoxiong ***@***.***>
发送时间: 2025年2月8日(周六) 中午1:43
收件人: ***@***.***>;
抄送: ***@***.******@***.***>;
主题: Re: [langgenius/dify] dify 升级后docker容器里的docker-api-1、docker-worker-1 您好,不好意思打扰,我是通过docker本地部署的dify,我根据指引升级dify到v0.10.2后,docker-api-1、docker-worker-1一直restarting,dify也无法登入,请问是什么问题呢? (Discussion #12312)
Check whether the Docker containers for api, worker, and sandbox are running. If any of them fail to start, edit the docker-compose.yaml file. Under the services section, add privileged: true to the corresponding service, such as api. Do the same for other services that fail to start. This should allow them to start normally.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
大佬们解决了嘛,同样的问题 |
Beta Was this translation helpful? Give feedback.
-
我的0.15.2版本的dify也是这样的问题(就nginx一直重启),但是不影响正常使用啊,然后我今天看到有新版本0.15.3,然后我dify更新至新版,就没有这样的问题了 |
Beta Was this translation helpful? Give feedback.
-
Self Checks
1. Is this request related to a challenge you're experiencing? Tell me about your story.
dify 升级后docker容器里的docker-api-1、docker-worker-1
您好,不好意思打扰,我是通过docker本地部署的dify,我根据指引升级dify到v0.10.2后,docker-api-1、docker-worker-1一直restarting,dify也无法登入,请问是什么问题呢?
2. Additional context or comments
No response
Beta Was this translation helpful? Give feedback.
All reactions