oier/ulicraft-server-v1
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore(uptime-kuma): bump image to :2

Browse Source 
The :1 image runs Node 18 (EOL), which gets no fix for the October 2026
Node.js security release. :2 migrates kuma.db in place on first start;
back up kuma_data per host before pulling (see plan/10-uptime-kuma.md).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
oierandClaude Opus 5.5 committed 2026-10-25 12:33:37 +01:00
1 parent d457713186
commit f4bd786140
2 files changed
+9 -3
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

docker-compose.yml
+1 -1
View File
@@ -376,7 +376,7 @@ services:
# Status monitoring + public status page. caddy proxies status. -> :3001. # Status monitoring + public status page. caddy proxies status. -> :3001.
# Joins mcnet so monitors probe the stack by internal service name. # Joins mcnet so monitors probe the stack by internal service name.
uptime-kuma: uptime-kuma:
image: louislam/uptime-kuma:1 image: louislam/uptime-kuma:2
container_name: uptime-kuma container_name: uptime-kuma
restart: unless-stopped restart: unless-stopped
volumes: volumes:
plan/10-uptime-kuma.md
+8 -2
View File
@@ -5,13 +5,13 @@
> card. Both ping `minecraft` over `mcnet` but serve different purposes. > card. Both ping `minecraft` over `mcnet` but serve different purposes.
Status monitoring + public status page. Service `uptime-kuma` Status monitoring + public status page. Service `uptime-kuma`
(`louislam/uptime-kuma:1`), web UI on `:3001`, reached only through caddy at (`louislam/uptime-kuma:2`), web UI on `:3001`, reached only through caddy at
`https://status.${BASE_DOMAIN}`. Joined to `mcnet`, so it can probe every other `https://status.${BASE_DOMAIN}`. Joined to `mcnet`, so it can probe every other
service by its internal container name. service by its internal container name.
## Add a Minecraft monitor ## Add a Minecraft monitor
Uptime Kuma 1.x ships a built-in **Minecraft Server** monitor type. It uses the Uptime Kuma ships a built-in **Minecraft Server** monitor type. It uses the
Server List Ping protocol (the same ping the vanilla multiplayer list uses): Server List Ping protocol (the same ping the vanilla multiplayer list uses):
unauthenticated, so it works fine with `ONLINE_MODE=FALSE` / unauthenticated, so it works fine with `ONLINE_MODE=FALSE` /
`ENFORCE_SECURE_PROFILE=FALSE`. It reports latency, online/max players, and MOTD. `ENFORCE_SECURE_PROFILE=FALSE`. It reports latency, online/max players, and MOTD.
@@ -53,6 +53,12 @@ monitor stays green. Run both to tell *server down* apart from *path broken*.
`https://auth.${BASE_DOMAIN}`, `https://distribution.${BASE_DOMAIN}`, `https://auth.${BASE_DOMAIN}`, `https://distribution.${BASE_DOMAIN}`,
`https://${BASE_DOMAIN}`, `https://files.${BASE_DOMAIN}` — a red `https://${BASE_DOMAIN}`, `https://files.${BASE_DOMAIN}` — a red
`distribution.` here explains client mod-mismatch join failures. `distribution.` here explains client mod-mismatch join failures.
- **1 → 2 upgrade (2026-10-25)** — moved off `:1`, whose image runs Node 18
(EOL, no fix for the Oct 2026 Node CVEs). The first `:2` start migrates
`kuma.db` in place (one-way, minutes on a ~140M DB; status page down until it
finishes — don't interrupt). Per host: `docker compose stop uptime-kuma`, tar
the `kuma_data` volume into `./backups/`, then `pull` + `up -d uptime-kuma`.
Rollback = restore the tarball + revert the tag to `:1`.
> **An HTTP monitor cannot see an SPA break.** It asserts "the server returned > **An HTTP monitor cannot see an SPA break.** It asserts "the server returned
> 200", which is a much weaker claim than "the app works". `files.` (Filestash) > 200", which is a much weaker claim than "the app works". `files.` (Filestash)