Open
Conversation
kenjenkins
reviewed
Apr 29, 2026
kenjenkins
left a comment
kenjenkins
left a comment
There was a problem hiding this comment.
Would it be better to stay consistent with upstream Envoy's minimum glibc requirement? According to the Envoy release notes, this is currently 2.30: https://github.com/search?q=repo%3Aenvoyproxy%2Fenvoy+%22glibc+%3E%3D%22&type=code.
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
2 participants
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.
Debian trixie uses glibc 2.41, which may cause compatibility issues when running pomerium outside of a container. The previous debian version uses 2.36, which is better but might still be incompatible with ubuntu 22.04 which uses 2.35. The current debian LTS uses 2.31. I'd prefer to use at least 2.34 so let's use ubuntu 22.04 as the base.