Update default_variant to trixie #2365

Activity

1. MikeMcC399 commented on Jan 30, 2026

   

   MikeMcC399

   on Jan 30, 2026

   ContributorAuthor

   More actions

   If this makes sense and is welcome I'll submit a PR to implement.
2. sxa commented on Jan 30, 2026

   

   sxa

   on Jan 30, 2026

   Member

   More actions

   I think it's ok having a distribution in active LTS be used so sticking with bookworm would be viable (Part of me wonders if explicitly sticking with one in the LTS phase is a good idea for stability!) but if we don't have a policy on these upgrades we should probably look at getting one defined.

   But given where we are at the moment, I'm personally ok with switching the default - do we need to announce such changes anywhere first?
3. MikeMcC399 commented on Jan 30, 2026

   

   MikeMcC399

   on Jan 30, 2026

   ContributorAuthor

   More actions

   @sxa

   if we don't have a policy on these upgrades we should probably look at getting one defined.

   That does seem to be a generally missing document that describes what's included, or not, and how changes are decided on.

   Regarding the update itself, perhaps just start with adding some text to the README?

   • stating that bookworm is the current default OS
   • describing the advantages / disadvantages of pinning or not pinning to a chosen OS
   • with a warning that the underlying default OS / version may change
   • and a mention of a future planning date for the transition from bookworm to trixie as default

   Instead of making the change now with no advanced warning, first choose a planning date and publish it.

   The EOL date for bookworm might be appropriate (2026-06-10, or the release of Node.js 26 (2026-04-22), for instance.
4. sxa commented on Jan 30, 2026

   

   sxa

   on Jan 30, 2026

   Last edited by sxa

   Member

   More actions

   The EOL date for bookworm might be appropriate

   I do wonder whether for Debian that June date isn't so much of a notable event since major architectures (arm and x64) should still receive public (without a subscription) support from a security perspective for much longer from the LTS team (so on that basis I wouldn't necessarily recommend that we stop publishing bookworm images in June)

   So basically we should also consider the policy for stopping old images as well as when to switch to new ones - worst case we continue publishing them until the OS goes out of public Long Term Support - which is likely when Dockerhub's official images would stop supporting it too.
5. MikeMcC399 commented on Jan 30, 2026

   

   MikeMcC399

   on Jan 30, 2026

   ContributorAuthor

   More actions

   @sxa

   This issue was only intended to be about setting the default image to trixie, not about stopping distributing bookworm based images when they are explicitly selected.

   Nevertheless it would definitely be helpful to put down some guidelines for Alpine and Debian about introduction and retirement based on upstream lifecycle dates. I don't believe that is described anywhere in this repo.

   👍React with 👍1Reacted by Stewart X Addison
6. MikeMcC399 commented on Feb 10, 2026

   

   MikeMcC399

   on Feb 10, 2026

   ContributorAuthor

   More actions

   I am going to close this issue, as it needs a more granular approach depending on the version of Node.js involved, and this would be part of a more general release cycle determination.
7. MikeMcC399

   closed this as not plannedon Feb 10, 2026