1Panel-dev / 1Panel-dev/1Panel

[Bug] OpenResty upgrade fails with exitCode=1 on 1.31.1.1-2-4-noble

Open
#13,688 3 comments 0 reactions 1 assignee View on GitHub

@wanghe-fit2cloud is already working on this.

Since Sep 2, 2026.

type: question
Dominant language
Go
Stars
37k
Forks
3.4k
Avg merge
9h 16m
Merged PRs (30d)
105

Description

Contact Information

No response

1Panel Version

v2.2.5(稳定版,专业版)

Problem Description

在阿里云 Ubuntu 服务器上,将 OpenResty 从 1.31.1.1-2-3-noble 升级到 1.31.1.1-2-4-noble 时,镜像拉取成功,但新容器启动后立即退出并被 Docker 自动重启,1Panel 判断容器未就绪并执行回滚。

同一台服务器、同一套 OpenResty 配置和端口下,回滚后的 1.31.1.1-2-3-noble 可以正常启动运行。

Steps to Reproduce
  1. 环境为 1Panel v2.2.5,OpenResty 当前版本为 1.31.1.1-2-3-noble
  2. 在应用商店将 OpenResty 升级到 1.31.1.1-2-4-noble
  3. 等待应用启动检查。
  4. 升级失败并自动回滚。
The expected correct result

新版本 OpenResty 容器应在保留现有配置、网站数据和 WAF 数据的情况下稳定启动,1Panel 应完成升级。

Related log output

2026/09/02 12:12:39 拉取镜像成功
2026/09/02 12:12:49 开始启动应用
2026/09/02 12:12:49 等待应用就绪
2026/09/02 12:12:50 等待应用就绪失败: container openresty is not ready: container restart count changed from 0 to 2 during startup
2026/09/02 12:12:50 升级应用 [openresty] 失败: container openresty is not ready: container restart count changed from 0 to 2 during startup
2026/09/02 12:12:50 开始应用 openresty 回滚
2026/09/02 12:13:04 应用 openresty 回滚成功

Docker daemon journal:

2026-09-02 12:12:49.792717 +0800 restarting container ... exitCode=1 ... restartCount=1 restartPolicy="{always 0}"
2026-09-02 12:12:50.316282 +0800 restarting container ... exitCode=1 ... restartCount=2 restartPolicy="{always 0}"
2026-09-02 12:12:50.847560 +0800 restarting container ... exitCode=1 ... restartCount=3 restartPolicy="{always 0}"

失败镜像摘要:
1panel/openresty:1.31.1.1-2-4-noble
sha256:1f3316a78af30040bd1e2bb4145957cae6492ecd0d525254ae761dbe289713bb

回滚后容器:
1panel/openresty:1.31.1.1-2-3-noble

Additional Information
  • 新镜像拉取成功,升级脚本执行成功。
  • 失败容器以 exitCode=1 退出,不是镜像拉取错误。
  • 主机根分区剩余约 21 GB;故障时段没有发现 OOM 或内核内存事件。
  • 新旧版本使用相同的 host 网络和 80/443 端口;回滚后旧版本正常运行,因此端口占用可能性较低。
  • 回滚后使用旧版本执行 openresty -t,配置语法检查成功。
  • 失败容器在回滚流程中被删除,当前无法再获取该容器的 stdout/stderr;烦请协助确认 -2-4-noble 是否存在启动回归,或是否与现有 1PWAF 持久化数据、挂载配置或模块兼容性有关。
  • 当前已保持回滚后的旧版本运行,未清空 WAF 数据或修改生产配置。

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.