ERPNEXT 无法正确部署/启动

Waiting for author response

PHPoling HuangFREE2天前

直接进入“崩溃重试中”（CrashLoopBackOff）。

3 条回复

JZJiyuan ZhengEMPLOYEE1天前

您好，

ERPNext 是一个比较重的应用，要排查 CrashLoopBackOff 需要实际的 log 跟 service ID。麻烦补上：

项目 ID 与 ERPNext service ID（从 Dashboard URL 获取）。
完整的 Runtime Logs（从容器启动到 crash 那一段的文字，贴上来即可）。
您部署在哪台服务器？是共享集群还是 dedicated server？如果是 dedicated，规格多大？

ERPNext 常见部署问题：

内存不足：ERPNext 本身就占用 2GB+，加上 MariaDB / Redis / Frappe 等服务一起跑，整台机器至少需要 4GB RAM，建议 8GB 起跳。如果是 2GB / 共享集群，几乎一定起不来。
数据库初始化失败：第一次启动会运行 bench new-site 之类的 migration，此步骤需要 MariaDB 已经 ready 才能运行，启动顺序错误会导致 crash。
环境变量设置错误：DB host / password / Redis URL 等变量要对应到内部 service endpoint。

把上面三项信息补上，我们可以帮您看具体是哪一个原因。

PHPoling HuangFREE1天前

项目 ID: project-6a0c5c5233d1a635fa37b3b5 服务 ID: service-6a0c5ca940a883532f3311ad 服务器位于 Wonder Mesh，机器配置为 6C/64GB 运行时日志: [Zeabur] Pod/service-6a0c5ca940a883532f3311ad-56fc459b5b-fwvd9 - Pulling: Pulling image "frappe/bench:latest"

[Zeabur] Pod/service-6a0c5ca940a883532f3311ad-56fc459b5b-fwvd9 - Pulled: Successfully pulled image "frappe/bench:latest" in 1.108s (1.108s including waiting). Image size: 929010383 bytes.

[Zeabur] Pod/service-6a0c5ca940a883532f3311ad-56fc459b5b-fwvd9 - Created: Created container: erpnext

[Zeabur] Pod/service-6a0c5ca940a883532f3311ad-56fc459b5b-fwvd9 - Started: Started container erpnext

[Zeabur] Pod/service-6a0c5ca940a883532f3311ad-56fc459b5b-fwvd9 - Pulling: Pulling image "frappe/bench:latest"

[Zeabur] Pod/service-6a0c5ca940a883532f3311ad-56fc459b5b-fwvd9 - Pulled: Successfully pulled image "frappe/bench:latest" in 1.104s (1.104s including waiting). Image size: 929010383 bytes.

[Zeabur] Pod/service-6a0c5ca940a883532f3311ad-56fc459b5b-fwvd9 - Created: Created container: erpnext

[Zeabur] Pod/service-6a0c5ca940a883532f3311ad-56fc459b5b-fwvd9 - Started: Started container erpnext

[Zeabur] Pod/service-6a0c5ca940a883532f3311ad-56fc459b5b-fwvd9 - BackOff: Back-off restarting failed container erpnext in pod service-6a0c5ca940a883532f3311ad-56fc459b5b-fwvd9_environment-6a0c5c52f3b70f2a79fbd6a0(1c546a65-358c-444d-acc0-4cf7d4ef725e)

[Zeabur] Pod/service-6a0c5ca940a883532f3311ad-56fc459b5b-fwvd9 - Pulling: Pulling image "frappe/bench:latest"

[Zeabur] Pod/service-6a0c5ca940a883532f3311ad-56fc459b5b-fwvd9 - Pulled: Successfully pulled image "frappe/bench:latest" in 1.121s (1.121s including waiting). Image size: 929010383 bytes.

[Zeabur] Pod/service-6a0c5ca940a883532f3311ad-56fc459b5b-fwvd9 - Created: Created container: erpnext

[Zeabur] Pod/service-6a0c5ca940a883532f3311ad-56fc459b5b-fwvd9 - Started: Started container erpnext

[Zeabur] Pod/service-6a0c5ca940a883532f3311ad-56fc459b5b-fwvd9 - BackOff: Back-off restarting failed container erpnext in pod service-6a0c5ca940a883532f3311ad-56fc459b5b-fwvd9_environment-6a0c5c52f3b70f2a79fbd6a0(1c546a65-358c-444d-acc0-4cf7d4ef725e)

CCanEMPLOYEE3小时前

您好，经查这是 ERPNext 社区模板的已知问题——模板配置的 Docker 镜像为 frappe/bench:latest（开发工具），而非正确的 frappe/erpnext 生产镜像，因此容器启动后会立即退出。

修复方式：

进入 ERPNext 服务的设置页面
将 Docker 镜像从 frappe/bench:latest 修改为 frappe/erpnext:v16
保存并重新启动服务

如果修改后仍有问题，请回复告知我们。

添加回复

论坛

3 条回复