-
Notifications
You must be signed in to change notification settings - Fork 263
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
fluent-bit:3.2.5-debug container is not a debug-variant but a minimal one #1498
Comments
@jeepee this issue was automatically closed because it did not follow the issue template |
Hi @jeepee! This workflow shows that our I'm not super familiar with these "debug" images -- but if you pull |
After some more digging I came to the same conclusion. Both the previous and the next tags are both working as expected, but that one does not. This issue will be resolved once a new release is made of the fluentbit package that is based on any other base-image besides 3.2.5-debug. |
Thanks for confirming. You may want to open an upstream issue so that the fluent-bit team is aware. While fluent-operator, by default, will use the |
we can bump fluent-bit version to the latest. |
The debug-container corresponding with release 3.2.5 is not actually a container image with debug-tools, but a minimal container without any binaries except the ones needed to run the fluent-bit and fluent-bit-watchers.
Inspecting the layers it seems like the debug variant only differs in the last two layers from the non-debug variant, which only contain the configuration-files and the binaries.
3.2.5:
3.2.5-debug:
The previous debug-container 3.1.8-debug was built as expected though:
The text was updated successfully, but these errors were encountered: