chore(docs): bump example Dockerfiles to Node 22 LTS + Caddy 2.11, SHA-pinned#260
Merged
Merged
Conversation
…A-pinned
Two improvements in one pass:
1. Bump base images to current LTS / stable. Today (2026-05-16):
- Node 18 LTS ended April 2025 — last `node:18-alpine` push was
2025-03-27, no security updates since.
- Node 22 is the current active LTS (until October 2027), refreshed
this week. → bumped 6 example Dockerfiles to `node:22-alpine`.
- Caddy 2.7 last updated May 2024; Caddy 2.11 is current stable.
→ bumped the 1 caddy example to `caddy:2.11-alpine`.
2. Pin every example FROM by `@sha256:<digest>`. Documentation examples
should model the secure practice we recommend for production —
readers copying these as a starting point now inherit a pinned,
deterministic, reproducible build. Closes the OpenSSF Scorecard
`Pinned-Dependencies` warnings for the 8 example Dockerfiles
(containerImage findings).
Digests used (resolved via Docker Hub registry API on 2026-05-16):
node:22-alpine sha256:757ec364de4d37cedf30871be2988927660834e656e9aa52aad9ac194814c30c
caddy:2.11-alpine sha256:3739ea4f0c877259a693d932693cf8f3408e9a9497c004f031b0e830e93e1546
Files touched (all in `docs/docs/examples/`):
advanced-configs/high-resource/Dockerfile
ecs-deployments/backend-service/Dockerfile
ecs-deployments/blockchain-service/Dockerfile
ecs-deployments/blog-platform/caddy.Dockerfile
ecs-deployments/meteor-app/Dockerfile (multi-stage: 2 FROM lines)
kubernetes-native/streaming-platform/Dockerfile
kubernetes-vpa/Dockerfile
Refs OpenSSF Scorecard climb plan in HARDENING.md.
Signed-off-by: Dmitrii Creed <creeed22@gmail.com>
Semgrep Scan ResultsRepository:
Scanned at 2026-05-16 11:29 UTC |
Security Scan ResultsRepository:
Scanned at 2026-05-16 11:30 UTC |
smecsia
approved these changes
May 16, 2026
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
2 participants
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.
Why
Docs/examples were teaching consumers an EOL pattern.
node:18-alpine→ EOL April 2025, last Docker Hub push 2025-03-27 (~14 months ago). No security updates since.node:22-alpineis the current active LTS (supported until October 2027), refreshed this week.caddy:2.7-alpinelast updated May 2024;caddy:2.11-alpineis current stable, refreshed this week.Two improvements in one pass:
docs/docs/examples/.FROMby@sha256:<digest>— modeling the secure-by-default practice we recommend for production. Anyone copying these as a starting point now inherits a pinned, deterministic, reproducible build.Side benefit — OpenSSF Scorecard
Closes 8 of the
Pinned-Dependencieswarnings (containerImage findings). Score should bump from 6/10 → ~7-8/10 on next Scorecard rescan.Digests used
Resolved via Docker Hub registry API on 2026-05-16:
node22-alpinesha256:757ec364de4d37cedf30871be2988927660834e656e9aa52aad9ac194814c30ccaddy2.11-alpinesha256:3739ea4f0c877259a693d932693cf8f3408e9a9497c004f031b0e830e93e1546Files touched
Test plan
Part of the OpenSSF score climb plan documented in HARDENING.md Phase 8.