[Dockerfile] Switch to wolfi/glibc based image #4261
+99
−116
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.
Hello ejabberd team,
@badlop as discussed some time ago, during a simple
processone/rtb
test with the Alpine/musl-libc based container image, I ran into issues when spawning 5-10k users on the container. After digging arround and spending some time, what effectively solved all issues was just using a glibc based variant and the container became well performing.Switching to the proposed wolfi/os image has the following qualities:
Additionally, the github workflows could drop the binary builds for
musl-libc
which have been the work-around also for the QEMU bug blocking buildingarm64
variants.Therefore, this PR includes:
wolfi
instead ofAlpine
package
imagesI was not yet able to test the workflows, maybe need to do some fine tuning here when they have been triggered.
Thanks and until soon!
Saarko