fix: Dockerfile build without gcc#413
Open
mamirpanah wants to merge 3 commits intoojo-network:umeefrom
Open
Conversation
adamewozniak
approved these changes
May 8, 2025
Author
|
@adamewozniak Hi can you merge this PR? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix: Build with CGO_ENABLED=0 to ensure static linking with musl
This PR fixes an issue where the build fails due to missing references to *64 functions (e.g., fstat64, lseek64) when linking statically with musl. The problem occurs because gcc is used by default, which is incompatible with musl for static builds.
The fix adds CGO_ENABLED=0 to the build command, forcing Go to use the internal linker and build a fully static binary with musl. This resolves the linking errors and ensures a successful build on Alpine Linux.
Changes:
Added CGO_ENABLED=0 to the make build command in the Dockerfile.