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
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.
The text was updated successfully, but these errors were encountered:
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 fixcosmonic-labs#16
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.
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.
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.
The text was updated successfully, but these errors were encountered: