Skip to content

chore: bump Debian base image from bullseye to bookworm - #42085

Open
ggazzo wants to merge 1 commit into
developfrom
chore/debian-base-bookworm
Open

ggazzo wants to merge 1 commit into
developfrom
chore/debian-base-bookworm

Conversation

@ggazzo

@ggazzo ggazzo commented Sep 9, 2026

Copy link
Copy Markdown
Member

Proposed changes (including videos or screenshots)

Bumps the base image of apps/meteor/.docker/Dockerfile.debian from the Debian 11 (bullseye) variant to the Debian 12 (bookworm) variant:

-FROM node:24.15.0-bullseye-slim
+FROM node:24.15.0-bookworm-slim

The Node version is intentionally not changed here — this PR is only the Debian variant move.

Why

1. bullseye is out of security support.
Debian 11 left regular support on 2024-08-15 and its LTS window ended on 2026-08-31 (Debian LTS wiki). From that date on, the Debian image we publish stops receiving OS security updates unless someone pays for ELTS. Bookworm is supported until 2028-06-30.

2. isolated-vm 6.x needs a full C++20 toolchain.
develop now pins isolated-vm@6.2.0 (since #41097 landed), which requires full C++20. The bullseye image only provides GCC 10.2, whose C++20 support is partial — so if that install ever falls back to a source compile instead of a prebuilt binary, the Debian image build breaks. Bookworm brings GCC 12 and glibc 2.36.

3. Toolchain parity with the alpine image.
Dockerfile.alpine already builds on alpine3.23 and gets a fully C++20-capable toolchain. This brings the Debian image in line rather than leaving the two published images on materially different compilers.

Verification

  • node:24.15.0-bookworm-slim exists on Docker Hub.
  • Reviewed the rest of Dockerfile.debian for anything Debian-11-specific: there is nothing pinned to bullseye. The apt packages installed (fontconfig, g++, make, python3, ca-certificates) all exist under the same names in bookworm, there are no third-party apt repos or pinned lib versions, and the deno stage copies a static binary from denoland/deno:bin-* (unaffected by the host distro, and a newer glibc is backward compatible for it).

Issue(s)

ARCH-1592

Steps to test or reproduce

Build the Debian image and confirm it starts:

docker build -f apps/meteor/.docker/Dockerfile.debian .

Further comments

Found while working on #41097 (Meteor 3.5 / Node 24) — raised there in this review comment. It is an independent base-image upgrade rather than part of the Meteor/Node bump, so it was split out into this PR to keep #41097 scoped. #41097 has since merged, so this now applies on top of Node 24.

No changeset. Matching precedent in this repo: the comparable image changes — #40536 (Node bump), #40389 (Meteor/Node bump) and #40128 (slim Docker image, which visibly changed the published image) — all landed without one, and there is no CI gate requiring a changeset. Happy to add one if maintainers want the base OS bump called out in the release notes.

Debian 13 (trixie) variants also exist for this Node version. Bookworm is the conservative step and the one raised in review; trixie can be a separate follow-up.

Summary by CodeRabbit

  • Chores
    • Updated the Debian-based build environment to use Debian Bookworm.

Task: ARCH-2405

@dionisio-bot

dionisio-bot Bot commented Sep 9, 2026

Copy link
Copy Markdown
Contributor

Looks like this PR is not ready to merge, because of the following issues:

  • This PR is missing the 'stat: QA assured' label

Please fix the issues and try again

If you have any trouble, please check the PR guidelines

@changeset-bot

changeset-bot Bot commented Sep 9, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 4aa5b87

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@ggazzo

ggazzo commented Sep 9, 2026

Copy link
Copy Markdown
Member Author

/jira ARCH-1592

@coderabbitai

coderabbitai Bot commented Sep 9, 2026

Copy link
Copy Markdown
Contributor

Review Change StackReview Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: 831b26e8-0321-45b8-af51-833990119ba3

📥 Commits

Reviewing files that changed from the base of the PR and between 9a4bfb5 and 4aa5b87.

📒 Files selected for processing (1)
  • apps/meteor/.docker/Dockerfile.debian

Included review availability: Your plan provides up to 10 included reviews per hour; 8 remain after this review.

📜 Recent review details
⏰ Context from checks skipped due to timeout. (3)
  • GitHub Check: Hacktron Security Check
  • GitHub Check: CodeQL-Build
  • GitHub Check: CodeQL-Build
🔇 Additional comments (1)
apps/meteor/.docker/Dockerfile.debian (1)

5-5: 🎯 Functional Correctness

No Node.js version change is required.

The repository supports Node.js 24.15.0 and declares it as the Volta version. The Docker image matches this supported runtime.


Walkthrough

The Debian Docker build changes its Node.js base image from Debian Bullseye slim to Debian Bookworm slim.

Changes

Docker base image

Layer / File(s) Summary
Update Debian base image
apps/meteor/.docker/Dockerfile.debian
The Dockerfile now uses node:24.15.0-bookworm-slim instead of node:24.15.0-bullseye-slim.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~2 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to 4aa5b

The Debian container now uses the Bookworm slim base image without an evidenced compatibility issue. The change is mergeable.

Suggested labels: type: chore

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and concisely describes the main change: updating the Debian base image from Bullseye to Bookworm.

Warning

Errors were encountered while retrieving linked issues.

Errors (1)
  • JIRA integration encountered authorization issues. Please disconnect and reconnect the integration in the CodeRabbit UI.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@ggazzo ggazzo added this to the 8.9.0 milestone Sep 9, 2026

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 1 file

Re-trigger cubic

Debian 11 (bullseye) left Debian LTS security support on 2026-08-31, so
the published Debian image no longer receives OS security updates.
Bookworm is supported until 2028-06-30 and ships GCC 12 / glibc 2.36,
matching the fully C++20-capable toolchain the alpine image already has.

Node version is intentionally unchanged.
@ggazzo
ggazzo force-pushed the chore/debian-base-bookworm branch from 9a4bfb5 to 4aa5b87 Compare September 9, 2026 18:22
@ggazzo

ggazzo commented Sep 9, 2026

Copy link
Copy Markdown
Member Author

/jira ARCH-1592

@codecov

codecov Bot commented Sep 9, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 69.46%. Comparing base (270e7eb) to head (4aa5b87).

Additional details and impacted files

Impacted file tree graph

@@             Coverage Diff             @@
##           develop   #42085      +/-   ##
===========================================
- Coverage    69.47%   69.46%   -0.02%     
===========================================
  Files         4300     4302       +2     
  Lines       171755   171764       +9     
  Branches     31069    31156      +87     
===========================================
- Hits        119329   119318      -11     
- Misses       47224    47262      +38     
+ Partials      5202     5184      -18     
Flag Coverage Δ
e2e 59.08% <ø> (+0.03%) ⬆️
e2e-api 46.27% <ø> (-0.01%) ⬇️
unit 71.20% <ø> (-0.02%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant