Please create static linux binaries
Summary
The files for 0.6.0 are all dynamically linked to glibc. (Fetched from https://release-cli-downloads.s3.amazonaws.com/v0.6.0/index.html)
Steps to reproduce
% file '/tmp/release-cli-linux-amd64'
/tmp/release-cli-linux-amd64: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, Go BuildID=RUF0-3LsEwvGbORQCrBS/Oroi7ocM9KV4H4kFwEdy/cE7Jd9BTkhDvc00xWwT0/H6LZZuFaUMYj3wOQvU2S, stripped
(older releases apparently used musl dynamically)
What is the expected correct behavior?
If the executable is to be used in environments without glibc/ldso then a static binary would be highly prefered.
Possible fixes
Glibc is unfortunately known to be problematic for static builds, building the project with musl as static binary would be ideal.
For reference https://medium.com/@diogok/on-golang-static-binaries-cross-compiling-and-plugins-1aed33499671
Edited by Jaime Martinez