Open candlerb opened 1 year ago
No, they should be statically linked. I'll take a look at this this evening.
Link to generic issue: https://github.com/golang/go/issues/57328
Any update on this?
Hi. sorry for the delay, I can't be quite as active on this project now. I have a solution that should make releases more reliable, but I need to find time to get a PR together. I'll try and get to it in the coming 2 weeks
@tcolgate Thx for the fast feedback! ✌️
Any update on this? Can you suggest the appropiate steps to build the app for older systems with older glibc versions? Or to build a system environment to run the binary with newer libc6 version? I've setup a chroot env with newer glib6 version, but Im not sure how this safe/stable is.
Found out the same yesterday. Compiled stuff from master and seems working now since the repo switched to a new buildpipeline... You can find from master compiled binaries in my issue. https://github.com/QubitProducts/exporter_exporter/issues/102
I was using exporter_exporter 0.4.2 binary just fine under Ubuntu 20.04.
But after upgrading to exporter_exporter 0.5.0 binary, it refuses to start:
Comparing the two binaries:
I find this odd, since I thought that in general, pure Go programs are statically linked. e.g.
I also notice that the Dockerfile has
Is it intentional that the exporter_exporter release binaries are dynamically linked? If so, perhaps they could be linked against an older version of GLIBC?