Re: Re: [DISCUSS] PIP-324: Alpine Docker images

2024-02-15 Thread Matteo Merli
H > > -Original Message- > From: Matteo Merli > Sent: Wednesday, February 14, 2024 2:01 PM > To: david.chris...@discordapp.com.invalid > Cc: dev@pulsar.apache.org > Subject: ''Re: Re: [DISCUSS] PIP-324: Alpine Docker images > > [You don't often get

Re: Re: [DISCUSS] PIP-324: Alpine Docker images

2024-02-15 Thread Alexander Hall
14, 2024 2:01 PM To: david.chris...@discordapp.com.invalid Cc: dev@pulsar.apache.org Subject: ''Re: Re: [DISCUSS] PIP-324: Alpine Docker images [You don't often get email from *REDACTED*. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ] Reviving

Re: Re: [DISCUSS] PIP-324: Alpine Docker images

2024-02-14 Thread Matteo Merli
Reviving the discussion thread. > For Netty, I think netty-transport-native-epoll is only built against > glibc ( https://netty.io/wiki/native-transports.html#using-the-linux-native-transport ). > Is there a workaround ? Yes, there is a workaround for Netty. It works perfectly fine by including

RE: Re: [DISCUSS] PIP-324: Alpine Docker images

2023-12-20 Thread David Christle
Are we sure the move to Alpine is worth the extensive performance testing and the risk of issues? Sticking with a popular glibc image like Temurin, Ubuntu/Debian, or ubi-minimal (mentioned also in this discussion) seems like a better path to me, without the risk of glibc vs musl issues. Using Di