Fix: Build static Go binary for Alpine compatibility #19
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.
Fixes issue #12.
Problem
The Docker image fails to run with the error
exec /bin/gitmal: no such file or directoryeven though the binary exists. This occurs because the Go binary is dynamically linked and expects glibc, but Alpine Linux uses musl libc. The misleading error actually indicates the dynamic linker (/lib64/ld-linux-x86-64.so.2) is not found.Solution
Set
CGO_ENABLED=0during the build to compile a statically linked binary that doesn't depend on external C libraries. This is the standard approach for Go binaries in Alpine-based containers.Changes
CGO_ENABLED=0to thego buildcommand in DockerfileTesting