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

Docker debug image, Fluent Bit 1.9: section 'in_exec' tried to instance a plugin name that don't exists #6236

Closed
Neki opened this issue Oct 19, 2022 · 1 comment · Fixed by fluent/fluent-bit-docs#943
Labels
docs issue Documentation Issue

Comments

@Neki
Copy link

Neki commented Oct 19, 2022

Bug Report

Describe the bug

The Fluentbit 1.9 Docker image does not start when the exec input plugin is used, even with the "debug" image.

To Reproduce

Run

docker run fluent/fluent-bit:1.9.9-debug /fluent-bit/bin/fluent-bit -i exec -p 'command=ls /etc' -o stdout

Output:

Fluent Bit v1.9.9
* Copyright (C) 2015-2022 The Fluent Bit Authors
* Fluent Bit is a CNCF sub-project under the umbrella of Fluentd
* https://fluentbit.io

[2022/10/19 08:24:43] [error] [config] section 'exec' tried to instance a plugin name that don't exists
[2022/10/19 08:24:43] [error] configuration file contains errors, aborting.

Expected behavior

The Fluent Bit container should start.

Your Environment

  • Version used: 1.9.9, "debug" Docker image
  • Configuration: see arguments above
  • Environment name and version: local (Mac M1, Apple Silicon)
  • Server type and version: N/A
  • Operating System and version: Mac OS 12.5.1
  • Filters and plugins: exec input plugin

Additional context

I'm trying to use the exec plugin in a configuration file, but Fluent Bit always fails with [error] [config] section 'in_exec' tried to instance a plugin name that don't exists.

The command line above is the simplest way to reproduce the error.

@patrick-stephens
Copy link
Contributor

The exec plugin is disabled for containers - it cannot work in the production image as it requires /bin/sh and the debug image uses the same binary as the production image.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs issue Documentation Issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants