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
go build -buildmode=c-shared -o out_gstdout.so out_gstdout.go
to run custom plugins. However, due to differences in the base libraries, such as the version of glibc between the runtime and build environments, the out_gstdout.so file may not work properly on other hosts.
Are there any possible solutions? I have tried using musl static linking, but it doesn't seem to work.
Fluent-bit provides the ability to develop plugins using Go(https://docs.fluentbit.io/manual/development/golang-output-plugins), and then compile them into a shared library with the command:
to run custom plugins. However, due to differences in the base libraries, such as the version of glibc between the runtime and build environments, the out_gstdout.so file may not work properly on other hosts.
Are there any possible solutions? I have tried using musl static linking, but it doesn't seem to work.
[2025/04/08 13:31:20] [error] [proxy] error opening plugin ./out_gstdout.so: '/lib/x86_64-linux-gnu/libc.so: invalid ELF header'
[2025/04/08 13:31:20] [error] [plugin] error loading proxy plugin: ./out_gstdout.so
The text was updated successfully, but these errors were encountered: