Provide docker images that can run on asahi-linux

[FlameFactory]

Is your feature request related to a problem? Please describe.

I'm using asahi-linux on Mac Book Pro M1 2021. I'm trying to pull & run arm64 image and I'm getting this error:

$ docker run --rm -it fluent/fluent-bit
<jemalloc>: Unsupported system page size
...
<jemalloc>: Unsupported system page size
Error in GnuTLS initialization: ASN1 parser: Element was not found.
<jemalloc>: Unsupported system page size
...
<jemalloc>: Unsupported system page size
[2024/05/07 16:51:21] [error] [/src/fluent-bit/src/config_format/flb_config_format.c:107 errno=12] Cannot allocate memory

Describe the solution you'd like

I wonder would it be a good thing to add 1 more image to build -- arm64 with 64k memory pages in jemalloc config (--with-lg-page=16)? And push it with custom docker tag, for example 3.0.3-arm64-64k

Describe alternatives you've considered

To be able to run fluent-bit on asahi-linux I have 2 options:

• clone repo & run docker build on asahi-linux, it's possible since jemalloc have hack for mac book M-chip laptops
• add parameter -DFLB_JEMALLOC_OPTIONS="--with-lg-page=16" to dockerfile and build it on any machine, and the image will be suitable for all known memory page sizes like 4k, 16k or 64k. For asahi-linux specifically --with-lg-page=14 will be enough, but it won't work for page size 64k for example.

Additional context

The problem is current arm64 images built with 4K memory page size in jemalloc config, but asahi-linux on M1 built with 16K memory size:

$ getconf PAGESIZE
16384

[patrick-stephens]

There are similar queries around Oracle Linux as well (check the issues). Yes we can, but the matrix of supported options becomes large and build times extend. We could do a custom tag potentially as you say so feel free to submit a PR for it.

[github-actions[bot]]

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days. Maintainers can add the exempt-stale label.

[github-actions[bot]]

This issue was closed because it has been stalled for 5 days with no activity.