Republish legacy SPFx images (1.12.1–1.14.0) on Node 14.21.3 to satisfy VS Code glibc >= 2.28 requirement#122
Draft
DonKirkham with Copilot wants to merge 3 commits into
Draft
Republish legacy SPFx images (1.12.1–1.14.0) on Node 14.21.3 to satisfy VS Code glibc >= 2.28 requirement#122DonKirkham with Copilot wants to merge 3 commits into
DonKirkham with Copilot wants to merge 3 commits into
Conversation
Copilot
AI
changed the title
[WIP] Fix compatibility issues for older images in VS Code
Plan legacy image refresh for VS Code compatibility
Jul 3, 2026
Copilot
AI
changed the title
Plan legacy image refresh for VS Code compatibility
Republish legacy SPFx images (1.12.1–1.14.0) on Node 14.21.3 to satisfy VS Code glibc >= 2.28 requirement
Jul 3, 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
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.
VS Code remote server (since March 2025) requires glibc >= 2.28. SPFx images 1.12.1–1.14.0 were built on
node:14.17.x/14.18.x/14.19.x(Debian 9/Stretch, glibc 2.24) and are therefore broken in devcontainer workflows.node:14.21.3is the latest Node 14 release and ships Debian 10/Buster (glibc 2.28).Changes
.github/workflows/build-and-push-legacy.yaml— newworkflow_dispatchworkflow to republish affected version tags without touchinglatestoronline:spfx_versionas a dropdown (1.12.1/1.13.0/1.13.1/1.14.0)FROMline:sed -i 's|^FROM node:.*|FROM node:14.21.3|' Dockerfilelinux/amd64+linux/arm64/v8and pushes the version tag onlynode:14.17.0(glibc 2.24)node:14.21.3(glibc 2.28)node:14.17.0(glibc 2.24)node:14.21.3(glibc 2.28)node:14.18.0(glibc 2.24)node:14.21.3(glibc 2.28)node:14.19.0(glibc 2.24)node:14.21.3(glibc 2.28)