You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As goreleaser uses goreleaser.Dockerfile, and that has no code to build the binary, my guess is that it adds the regular binary-build instead of a static one:
ISSUE TYPE
BUG REPORT
SUMMARY
The Docker container at ghcr.io contains a dynamically built
/kubebuilder
binary, and is missing the required libraries.ENVIRONMENT
STEPS TO REPRODUCE
EXPECTED RESULTS
The
/kubeaudit
binary actually starts.ACTUAL RESULTS
The
/kubeaudit
binary cannot be started.ADDITIONAL INFORMATION
Inspection of the container shows that the binary is dynamically linked, and the required binaries are missing:
As
goreleaser
usesgoreleaser.Dockerfile
, and that has no code to build the binary, my guess is that it adds the regular binary-build instead of a static one:Building the container using
Dockerfile
results in a working, static/kubeaudit
:FEATURE IDEA
Proposal:
Use
Dockerfile
withgoreleaser
, or even better: havegoreleaser
build the separate binaries as static as well.The text was updated successfully, but these errors were encountered: