feat(docker): upgrade Kuma to 2.5.0 on the upstream rootless image - #42
Merged
Conversation
There was a problem hiding this comment.
Pull request overview
This PR updates the container image used to run Uptime Kuma by upgrading the upstream base image from 2.3.2 to 2.5.0 and switching to the upstream-supported -rootless variant so the non-root runtime contract is maintained by upstream rather than enforced locally in our Dockerfile.
Changes:
- Bump
UPTIME_KUMA_VERSIONfrom2.3.2→2.5.0. - Switch base image from
louislam/uptime-kuma:${UPTIME_KUMA_VERSION}tolouislam/uptime-kuma:${UPTIME_KUMA_VERSION}-rootless. - Remove the explicit
USER nodedirective since the rootless upstream image already setsUSER=nodeand prepares/app/data.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
andres-pcg
force-pushed
the
feat/kuma-2.5.0-rootless
branch
from
August 21, 2026 07:41
9b6d676 to
d83958d
Compare
The -rootless variant is upstream's supported non-root image (same USER node contract we added by hand), so the guarantee survives future version bumps without local patching.
andres-pcg
force-pushed
the
feat/kuma-2.5.0-rootless
branch
from
August 21, 2026 07:45
d83958d to
af32cb1
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #44.
Stacked on #37 (auto-retargets to
mainwhen it merges). Upgrades 2.3.2 → 2.5.0 and switches the base to upstream's-rootlessvariant.Why rootless-variant instead of our own
USER nodeUpstream has published
-rootlessimages for every release since 2.0 (2.5.0-rootlessinspected:User=node,/app/datachowned to node, same entrypoint/healthcheck). Same effect as #37'sUSER node, but the non-root contract is maintained upstream — future version bumps can't silently regress it on our side.What 2.4.0 + 2.5.0 bring us (we skip 2.4.0)
stat_dailyup/down columns widened SMALLINT → unsigned INTEGER (auto-migration on first boot).Verification (local, image built from this branch)
uid=1000(node); HTTP up;extra/healthcheck200; containerHEALTHCHECKhealthy; log showsUptime Kuma Version: 2.5.0; zero error lines with/app/dataon a tmpfs like Cloud Run's in-memory volume.v2.5.0→substring(0,2)=v2→ sameuptime-kuma-v2service, in-place revision; LB/NEG untouched.