GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Add OS maintenance strategy to documentation · Issue #2397 · nodejs/docker-node

Add OS maintenance strategy to documentation #2397

New issue
Copy link
New issue
Copy link
Open
Open
Add OS maintenance strategy to documentation#2397
Copy link

Description

@MikeMcC399
MikeMcC399
opened on Mar 4, 2026
Issue body actions

Suggestion

Extend the CONTRIBUTING document to describe the strategy for including and adding new images, either by adding text or referring to a separate new document.

This should reference:

  • which operating systems are included (currently Alpine and Debian)
  • how / when new operating system versions are added
  • how / when operating system versions are removed
  • how the default operating system version is set and maintained for a given Node.js release line
  • how the default Node.js version is set and maintained for a given operating system selection
  • how architectures will be added / maintained / removed
  • if supported architectures change during the lifecycle of Node.js / operating system versions, describe how these will be handled

Related

#2363

Activity

  1. MikeMcC399 commented on Mar 4, 2026

    @MikeMcC399
    MikeMcC399
    on Mar 4, 2026
    ContributorAuthor
    More actions

    For Debian, suggestion submitted as #2398

  2. yosifkit commented on Mar 4, 2026

    @yosifkit
    yosifkit
    on Mar 4, 2026
    Contributor
    More actions

    More points to consider (which are both bounded by which architectures parent images support)

    • how / when architectures are removed
      • For example, when Debian releases move from "release architecture" to "LTS", they usually drop to a more limited set of architectures.
    • how / when architectures are added
    Reacted by Mike McCready, Stewart X Addison and surajtaghash
  3. MikeMcC399 commented on Mar 6, 2026

    @MikeMcC399
    MikeMcC399
    on Mar 6, 2026
    ContributorAuthor
    More actions

    @yosifkit

    Thanks! I've added your suggestions to the list in a generic form.

    Reacted by yosifkit
  4. MikeMcC399 commented on Aug 24, 2026

    @MikeMcC399
    MikeMcC399
    on Aug 24, 2026
    ContributorAuthor
    More actions

    More points to consider (which are both bounded by which architectures parent images support)

    • how / when architectures are removed

      • For example, when Debian releases move from "release architecture" to "LTS", they usually drop to a more limited set of architectures.

    Added through PR #2609 for Debian. CONTRIBUTING > Version Updates is updated with information concerning Debian releases and lifecycle transitions.

    • how / when architectures are added

    That aspect is still not completely described

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.