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

[BUG] netreap 0.1.2 doesn't run on Amazon Linux 2. #16

Closed
deverton-godaddy opened this issue Jun 19, 2023 · 1 comment
Closed

[BUG] netreap 0.1.2 doesn't run on Amazon Linux 2. #16

deverton-godaddy opened this issue Jun 19, 2023 · 1 comment
Labels
bug Something isn't working help wanted Extra attention is needed

Comments

@deverton-godaddy
Copy link
Contributor

I haven't dug in to this yet, but switching from the 0.1.0 release to the 0.1.2 release results in netreap failing to start with the below error.

/usr/bin/netreap: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /usr/bin/netreap)
/usr/bin/netreap: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /usr/bin/netreap)

No other changes to configuration were made. Reverting to the 0.1.0 release works fine.

These instances are running on Amazon Linux 2 which ships with glibc 2.26. I'm guessing that the netreap builds are using cgo and are running on systems that are using a newer glibc.

@deverton-godaddy deverton-godaddy added bug Something isn't working help wanted Extra attention is needed labels Jun 19, 2023
@deverton-godaddy
Copy link
Contributor Author

Looks like this is probably related to golang/go#58550

deverton-godaddy added a commit to deverton-godaddy/netreap that referenced this issue Jul 6, 2023
As part of the Go 1.20 release it seems like the default for `CGO_ENABLED` is no longer carried over from the tools. This leads to linking issues on systems that use different versions of glibc from what the base image uses. See golang/go#58550 for more details.

This change should fix cosmonic-labs#16
protochron added a commit that referenced this issue Jul 31, 2023
It looks like the maintainers of the Go Docker image decided to switch
to base their images off of Debian Bookworm instead of Bullseye. This
meant that `golang-1.20` pulled an image with a newer version of glibc
which only broke when trying to run the image.

This is a quick fix that explicitly calls for the Bullseye version of
the build image.

Closes #22, #16.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working help wanted Extra attention is needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant