-
Notifications
You must be signed in to change notification settings - Fork 1k
Alpine target binary is missing symbols #726
Comments
Further investigation reveals that for the Please comment here if we got something wrong, or if you can confirm this is the expected behaviour. |
+1 If users are expected to make environments ready for your produced binaries by installing prerequisites to use the binary ? that is defeating the entire purpose of there being a binary release of the software.. I.e. until the binary release is working standalone as designed, we users cannot use software packaged by this at all in most circumstances a binary release would be required (i.e. environments that are unable to install said prerequisite/s) |
I've run into this problem in mapbox/ecs-watchbot#327 (comment). However, @adrukh's suggested workaround of adding This came up after switching from a pkg |
Adding the following two libs got the binary working for me. I'd love a way to compile them in statically though, any thoughts?
|
Does anyone has an issue that alpine binary just runs and quits immediately? I added the libstdc++ and libgcc. I have express server inside and on Windows everything works just fine |
This issue has been resolved. Please let me know if it is still relevant. |
👋 and thank you so much for this valuable project! We've been using it successfully for the past 2 years, and really appreciate the hard work behind it!
We're facing an issue where building our project for the
alpine
platform generates a binary file thatsegfaultshas missing symbols when executed.Our workaround is to spin up analpine
container and build our project inside it for thealpine
platform. This generates a proper binary.This wasn't really the workaround, it's just that
node:alpine
includeslibstdc++
, andalpine:latest
doesn't.Our project is https://github.com/snyk/snyk,
and our workaround is described here - snyk/cli#608and we now simply build against thealpine
target.1. How can we help troubleshoot and fix this issue?2. If you are facing something similar, please see if our workaround can help you.
The text was updated successfully, but these errors were encountered: