Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Set env CGO_ENABLED=0 for goreleaser to avoid dynamic linking #1293

Merged
merged 1 commit into from Aug 16, 2022
Merged

Set env CGO_ENABLED=0 for goreleaser to avoid dynamic linking #1293

merged 1 commit into from Aug 16, 2022

Commits on Aug 12, 2022

  1. Set env CGO_ENABLED=0 for goreleaser to avoid dynamic linking 

    Binaries that are being built by the goreleaser don't have the CGO_ENABLED=0 env set which means they are dynamically linked to 
/lib64/ld-linux-x86-64.so.2  (or whichever version of ld-linux)
In some versions of distros, there are different versions ld-linux which makes the swag not start properly. 
In my case, I wanted to download the release binary into intermediate docker based on alpine to generate API documentation and it was always failing with "file not found" error.
NOTE: This change was not tested - I don't have the whole setup to test the goreleaser
sources:
https://jvns.ca/blog/2021/11/17/debugging-a-weird--file-not-found--error/
https://goreleaser.com/customization/build/
    @csiwek
    csiwek committed Aug 12, 2022
    Copy the full SHA
    d1992e1 View commit details
    Browse the repository at this point in the history