直接進入「崩潰重試中」
直接進入「崩潰重試中」
您好,
ERPNext 是個比較重的應用,要排查 CrashLoopBackOff 需要實際的 log 跟 service ID。麻煩補上:
ERPNext 常見部署問題:
bench new-site 之類的 migration,這步驟需要 MariaDB 已經 ready 才能跑,啟動順序錯誤會導致 crash。把上面三項資訊補上,我們可以幫您看具體是哪一個原因。
專案ID: project-6a0c5c5233d1a635fa37b3b5
服務ID: service-6a0c5ca940a883532f3311ad
伺服器為 Wonder Mesh 的,機器本身是 6C/64GB
Runtime Log:
[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 - 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)
[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)
您好,經查這是 ERPNext 社群模板的已知問題——模板配置的 Docker 映像檔是 frappe/bench:latest(開發工具),而不是正確的 frappe/erpnext 生產映像,所以容器啟動後會立刻退出。
修正方式:
frappe/bench:latest 改為 frappe/erpnext:v16如果改完仍有問題,請再回覆讓我們知道。