[PR #1010] [MERGED] fix(openpanel): pin verified 2.2.1 images to prevent broken-release breakage #16318

New Issue

GiteaMirror · 2026-07-14T23:19:06-05:00

GiteaMirror commented

2026-07-14 23:19:06 -05:00

📋 Pull Request Information

Original PR: https://github.com/Dokploy/templates/pull/1010
Author: @Siumauricio
Created: 7/14/2026
Status: ✅ Merged
Merged: 7/14/2026
Merged by: @Siumauricio

Base: canary ← Head: fix/openpanel

📝 Commits (1)

f946051 fix(openpanel): pin verified 2.2.1 images and fix ClickHouse interserver host

📊 Changes

3 files changed (+5 additions, -5 deletions)

View changed files

📝 blueprints/openpanel/docker-compose.yml (+3 -3)
📝 blueprints/openpanel/meta.json (+1 -1)
📝 blueprints/openpanel/template.toml (+1 -1)

📄 Description

What is this PR about?

Fixes the OpenPanel template reported broken in #615 ("It's error when use OpenPanel 2.0.0").

Root cause

When #615 was filed (Dec 2025), the template had just been migrated to the freshly released 2.0.0 images (#594), which were broken/unstable at that point; the template later moved to the mutable :2 tag (#680), which leaves it exposed to the same failure mode whenever upstream pushes a new 2.x release. The reporter's environment (CentOS 7, kernel 3.10, EOL) is also below what modern ClickHouse supports, which can independently cause the deploy-time error.

Changes

Pin lindesvard/openpanel-api|dashboard|worker to 2.2.1 (current upstream stable, released 2026-03-21) instead of the mutable :2 tag, so a future broken 2.x release cannot silently break the template again.
Fix ClickHouse interserver_http_host from opch to the actual service name op-ch (matches upstream self-hosting config).
Set meta.json version to the pinned 2.2.1.

Verification (deployed on a Dokploy instance)

Fresh template deploy with the pinned images completes successfully:

Deploy status: done, all 6 containers running with 0 restarts (op-db, op-kv, op-ch, op-api, op-dashboard, op-worker)
GET / → 302 → /login, renders "Login | OpenPanel.dev"
GET /onboarding → 200, renders "Create an account | Getting Started | OpenPanel.dev"
GET /api/healthcheck → {"ready":true,"redis":true,"db":true,"ch":true} (Postgres migrations, Redis and ClickHouse init all OK)

For reference, the template was also re-deployed with 2.0.0 pinned (the version from the issue) on the same instance and it now deploys fine too — confirming the original failure came from the early 2.0.0 images / unsupported host OS rather than the template structure. node build-scripts/generate-meta.js --check passes (476 templates validated).

Closes #615

🤖 Generated with Claude Code

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/Dokploy/templates/pull/1010 **Author:** [@Siumauricio](https://github.com/Siumauricio) **Created:** 7/14/2026 **Status:** ✅ Merged **Merged:** 7/14/2026 **Merged by:** [@Siumauricio](https://github.com/Siumauricio) **Base:** `canary` ← **Head:** `fix/openpanel` --- ### 📝 Commits (1) - [`f946051`](https://github.com/Dokploy/templates/commit/f946051a6ced8b9ad170b2a9665d9f8e26db3cdb) fix(openpanel): pin verified 2.2.1 images and fix ClickHouse interserver host ### 📊 Changes **3 files changed** (+5 additions, -5 deletions) <details> <summary>View changed files</summary> 📝 `blueprints/openpanel/docker-compose.yml` (+3 -3) 📝 `blueprints/openpanel/meta.json` (+1 -1) 📝 `blueprints/openpanel/template.toml` (+1 -1) </details> ### 📄 Description ## What is this PR about? Fixes the OpenPanel template reported broken in #615 ("It's error when use OpenPanel 2.0.0"). ### Root cause When #615 was filed (Dec 2025), the template had just been migrated to the freshly released `2.0.0` images (#594), which were broken/unstable at that point; the template later moved to the mutable `:2` tag (#680), which leaves it exposed to the same failure mode whenever upstream pushes a new 2.x release. The reporter's environment (CentOS 7, kernel 3.10, EOL) is also below what modern ClickHouse supports, which can independently cause the deploy-time error. ### Changes - Pin `lindesvard/openpanel-api|dashboard|worker` to **2.2.1** (current upstream stable, released 2026-03-21) instead of the mutable `:2` tag, so a future broken 2.x release cannot silently break the template again. - Fix ClickHouse `interserver_http_host` from `opch` to the actual service name `op-ch` (matches upstream self-hosting config). - Set `meta.json` version to the pinned `2.2.1`. ### Verification (deployed on a Dokploy instance) Fresh template deploy with the pinned images completes successfully: - Deploy status: `done`, all 6 containers running with 0 restarts (op-db, op-kv, op-ch, op-api, op-dashboard, op-worker) - `GET /` → 302 → `/login`, renders "Login | OpenPanel.dev" - `GET /onboarding` → 200, renders "Create an account | Getting Started | OpenPanel.dev" - `GET /api/healthcheck` → `{"ready":true,"redis":true,"db":true,"ch":true}` (Postgres migrations, Redis and ClickHouse init all OK) For reference, the template was also re-deployed with `2.0.0` pinned (the version from the issue) on the same instance and it now deploys fine too — confirming the original failure came from the early 2.0.0 images / unsupported host OS rather than the template structure. `node build-scripts/generate-meta.js --check` passes (476 templates validated). Closes #615 🤖 Generated with [Claude Code](https://claude.com/claude-code) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

GiteaMirror added the pull-request label 2026-07-14 23:19:06 -05:00

GiteaMirror closed this issue

2026-07-14 23:19:07 -05:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/templates#16318