lfg2025/kaiser-natron
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: use valid pinned node image tag

Browse Source 
node:24.13.0-alpine3.20 was never published to Docker Hub, so the
Portainer build failed on pull. Switch to node:24.15.0-alpine3.23
(current Node 24 line on current Alpine line) and update README.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This commit is contained in:
Dorian
2026-04-21 11:36:01 +01:00
parent 9bc6b842cf
commit fdc871859b
2 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
Dockerfile
View File

@@ -3,7 +3,7 @@
# Pinned tags only — no :latest, no floating minors.
# ── 1. Build ───────────────────────────────────────────────────────────────
FROM node:24.13.0-alpine3.20 AS build
FROM node:24.15.0-alpine3.23 AS build
WORKDIR /app
# Copy lockfile first so `npm ci` layer caches when only source changes.

2
README.md
View File

@@ -36,4 +36,4 @@ Portainer builds the image from the `Dockerfile` at the repo root each time the
3. Deploy. The site comes up on host port **5555** (internal container port 80).
4. Health: `GET /health` returns `200 ok`.
Pinned images: `node:24.13.0-alpine3.20` (build stage), `nginx:1.27.3-alpine` (serve stage). Bump explicitly when you want to upgrade — no floating tags.
Pinned images: `node:24.15.0-alpine3.23` (build stage), `nginx:1.27.3-alpine` (serve stage). Bump explicitly when you want to upgrade — no floating tags.