Unable to load native binding qwik.linux-x64-gnu.node

[Nefcanto]

This is my Dockerfile to create a node-based image with dependencies installed:

FROM node:lts-bookworm-slim

RUN sed -i 's/^Components: main$/& contrib non-free-firmware/' /etc/apt/sources.list.d/debian.sources

ENV PATH="${PATH}:/Commands/SiteContainer:/Commands"

RUN npm install -g depcheck \
    && npm install -g lighthouse

COPY . /Site

RUN cd /Site \
    && rm -rf package-lock.json \
    && npm install --legacy-peer-deps \
    && mkdir /npm \
    && mv /Site/node_modules /npm \
    && rm -rf /Site

But now I get this error when I start a container from this image:

Unable to load native binding qwik.linux-x64-gnu.node. Falling back to wasm build. /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by /npm/node_modules/@builder.io/qwik/bindings/qwik.linux-x64-gnu.node)
using deprecated parameters for the initialization function; pass a single object instead

What should I do?

[wmertens]

This is mostly harmless, it means that the optimizer build needs the glibc version that it can't find, and that instead it will be optimizing using the wasm build.

However, I thought that the optimizer binaries were stand-alone, no libraries required, so that's still a little puzzling.

[Nefcanto]

@wmertens thank you for the quick response.
If that optimizer is better, why not we also use it. We crave speed.

[wmertens]

I'm going to close it because we can't really do anything about this. The wasm build works and the native build requires a glibc library that is missing. Building that library into the binary would probably make the package several MB larger still.

[Nefcanto]

@wmertens, getting warnings for the rest of the lifecycle of a framework is not a good decision. Is there a way to suppress this warning?