Certain node_modules libraries break because of alpine vs ubuntu base images about meteor-base HOT 3 CLOSED

Are you using https://github.com/disney/meteor-base/blob/main/example/app-with-native-dependencies.dockerfile? There are three base images there; the middle one compiles your app dependencies in an Alpine context. This is mentioned in https://github.com/disney/meteor-base#step-1-bootstrap-dockerfile-from-template.

If this doesn’t address your issue, please provide a minimal reproduction. You can also search this repo for issues related to “bcrypt,” as that’s a very commonly used native dependency that has tripped people up in the past.

from meteor-base.

Hey there!

We're experiencing this issue: monti-apm/meteor-profiler#6

The problem seems to be that v8-profiler-next gets compiled against glibc (Debian) and then ran against musl (Alpine). Or it might just be that it doesn't like musl.

Anyway, using Debian as a final image resolved the issue: Refty/lemverse@68f5ff9

I've tried the app-with-native-dependencies.dockerfile as well, but it doesn't change anything since the npm deps are still built on Debian and ran on Alpine.

Please consider reopening this issue and either base this repository's src/Dockerfile on Alpine, or modify examples so that they're using a slim Debian instead of Alpine. :)

PS – Debian slim images are only 10MB or so larger than Alpine images, but tend to be much more stable (glibc is much more widely used and supported than musl).

from meteor-base.

If you look at

from meteor-base.