Avoid upgrading base OS image during the life of a major version of Node.js
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 8.6k
- Forks
- 2k
- Avg merge
- 10h 19m
- Merged PRs (30d)
- 16
Description
Problem
The update of the base OS image used for node:18 from Debian 11 to 12 has caused issues for various people:
- https://github.com/nodejs/node/issues/43064#issuecomment-1591237820 (last comments)
- https://github.com/nodejs/docker-node/issues/1916
- https://github.com/nodejs/build/issues/3382
Solution
Keep the same base OS image during the entire life of any major version of Node.js and only upgrade it for future major versions.
Alternatives to Consider
Teach the community to specify the name of the base OS in their Dockerfiles, but I'm afraid it's too late for that. I don't remember seeing any documentation that recommends to do it.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating the Docker image build and release configuration for node:18, then trace how its base OS is selected across major-version releases. Done means the base OS remains unchanged for a Node.js major version while future major versions can adopt a newer image.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, node.js
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100