-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
1.9.9: exec input not available or crashes because of parser not found #6436
Comments
Oh I see, in the Docker image, exec input is not enabled- why? https://github.com/fluent/fluent-bit/blob/master/dockerfiles/Dockerfile#L71 |
This issue does not occur on the AWS release of 1.9.9:
|
I also got a segfault when building FLB from source: https://gist.github.com/PettitWesley/4c141146837b2ac962edc498b41eb711 So this and the weird parser load is the only unresolved issue:
I just compiled latest v1.9.9 tag with CMake flags |
Exec is disabled as it does not function in distroless containers - it requires the existence of There is an issue on it all somewhere, let me dig it out. |
#4719 is the change, it links out to the issue. The docs do cover it: https://docs.fluentbit.io/manual/pipeline/inputs/exec#container-support |
Is this your issue as well @PettitWesley ? #5848 |
@PettitWesley Could you check a patch #5720 ? |
@nokute78 Thanks! I think that possibly explains what I was seeing |
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days. Maintainers can add the |
This issue was closed because it has been stalled for 5 days with no activity. |
Bug Report
I'm having weird issues on 1.9.9 with the exec input that honestly do not make sense.
fluent-bit.conf:
On a separate dev instance compiling Fluent Bit and running it directly I get:
I am not sure what is going wrong here... am I doing some obviously wrong?
Also not sure how I am getting different results on different machines/deployments of 1.9.9
The text was updated successfully, but these errors were encountered: