-
Notifications
You must be signed in to change notification settings - Fork 94
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.
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
🐛 enable the use of CGO #246
Conversation
Signed-off-by: Yang Le <yangle@redhat.com>
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: elgnay The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Codecov ReportPatch coverage has no change and project coverage change:
Additional details and impacted files@@ Coverage Diff @@
## main #246 +/- ##
==========================================
+ Coverage 60.35% 60.37% +0.02%
==========================================
Files 132 132
Lines 13590 13590
==========================================
+ Hits 8202 8205 +3
+ Misses 4633 4631 -2
+ Partials 755 754 -1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
do we know if it works with ARM? cc @haoqing0110 |
Verified on arm64, all the images work fine when cgo enabled. Below are the output of registration-operator as an example:
|
@elgnay could we set this as an optional env var, so we can choose to build with or without CGO (disabled by default) |
As we can see from the golang doc: https://tip.golang.org/doc/go1.20. The default value of CGO_ENABLED depends on the build environment. It's hard to set a default value in the Makefile. So I'm closing this PR. If anyone wants to enable the use of CGO, a custom Dockerfile is required with
|
Summary
Related issue(s)
Fixes #