Replace EOL Debian Buster with Bullseye in Dockerfile-node
#47204
Conversation
This file contains 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
avatus
approved these changes
Oct 4, 2024
kimlisa
approved these changes
Oct 4, 2024
public-teleport-github-review-bot
bot
removed request for
zmb3,
bl-nero and
jakule
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
This was referenced Oct 7, 2024
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.
Electron upgrade to version 32.1.2 failed because Electron started requiring GCC v10:
While we could probably install it, I noticed that the Buster image we use, went EOL some time ago nodejs/docker-node#2114.
Updating to Bullseye resolves the problem with GCC version.
The only downside is that it increases the glibc requirement, from 2.29 to 2.31. However, this should not have a minimal impact on users, for example, Ubuntu 20.04 LTS has glibc 2.31.
Successful tag build https://github.com/gravitational/teleport.e/actions/runs/11180298411/job/31081783865
changelog: Teleport Connect for Linux now requires glibc 2.31 or later