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.

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

loxilb go code build error in BPFire chroot build environment #674

Closed
vincentmli opened this issue May 12, 2024 · 1 comment
Closed

loxilb go code build error in BPFire chroot build environment #674

vincentmli opened this issue May 12, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@vincentmli
Copy link

Describe the bug

I am able to build loxicmd in BPFire chroot build environment, but not loxilb. this is unlikely bug in loxilb but golang in chroot build environment, but would like to know if there is workaround in loxilb to avoid this problem

two problems:

  1. loxilb go.mod:3: invalid go version '1.22.0': must match format 1.23

BPFire has golang 1.20.4 installed in chroot build environment, loxilb go.mod has 1.22.0 requirement, it seems cause above mismatch? see error vincentmli/BPFire#19

  1. loxilb main.go build error GOPROXY list is not the empty string

I upgraded BPFire golang from 1.20.4 to 1.22.0 to meet loxilb go.mod requirement, but then had this main.go:24:2: GOPROXY list is not the empty string, but contains no entries, see vincentmli/BPFire#17, google search shows golang upgrade could result in this problem, not sure how to workaround this issue.

To Reproduce
Steps to reproduce the behavior:

I can prepare the BPFire build tar balls (about 4 Gigabyte) if you are interested to reproduce

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Environment (please complete the following information):

  • OS: Ubuntu 22.04 to build BPFire loxilb addon in chroot

  • LoxiLB Version: 0.9.4-beta

Additional context
Add any other context or topology about the problem here.

it is better to build loxilb in BPFire chroot environment as BPFire software addon, build loxilb and copy binary to BPFire OS seems not ideal

@vincentmli vincentmli added the bug Something isn't working label May 12, 2024
@vincentmli
Copy link
Author

I used go mod vendor for loxilb and loxicmd to get the golang packages dependencies which created vendor under loxilb and loxicmd, this avoid to download the golang packages, and avoid the GOPROXY list is not the empty string issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant