[fix] Remove gcompat from the Alpine based image since real glibc is installed #23374
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.
Motivation
In 3.3.1 and 4.0.0-preview.1 images, Conscrypt cannot be loaded. Jetty uses it for native OpenSSL based TLS.
This caused a problem described in #23364 where the warning log message "2024-09-27T19:25:20,336+0000 [main] WARN org.apache.pulsar.common.util.SecurityUtility - Conscrypt isn't available for Linux amd64. Using JDK default security provider." broke pulsar-admin output parsing in other scripts.
The problem was addressed by setting log level to
debug
.While investigating the issue, it appeared that musl + gcompat and glibc in Alpine shouldn't be mixed at runtime in dynamic linking. It's not recommended to mix musl and glibc either.
However, for the Conscrypt case, the loading of the library works when
gcompat
is removed. There shouldn't be a reason to havegcompat
exist with the current realglibc
solution in Alpine.Modifications
gcompat
package from Alpine.Documentation
doc
doc-required
doc-not-needed
doc-complete