Skip to content

Fix 1090: Path issues #1093

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

Conversation

sarathchandra24
Copy link
Collaborator

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #1090

Does this PR introduced a user-facing change?

Fixes docker run path for fluentd

docker run kubesphere/fluentd:v1.15.3-arm64

is running the following
image

This changes fixes the path issue for fluentd
image

Additional documentation, usage docs, etc.:


Signed-off-by: Sarath Chandra Oruganti <[email protected]>
@sarathchandra24 sarathchandra24 self-assigned this Mar 15, 2024
@benjaminhuo
Copy link
Member

benjaminhuo commented Apr 4, 2024

@sarathchandra24 Will your fix work for amd64 as well?
cc @elliottpope

@benjaminhuo
Copy link
Member

@sarathchandra24 Will your fix work for amd64 as well? cc @elliottpope

Merge this for now, it'll be great if @sarathchandra24 @elliottpope you can create another PR if the path doesn't work for amd64

@benjaminhuo benjaminhuo merged commit e5e2c59 into fluent:master Apr 4, 2024
@Hayajiro
Copy link

@sarathchandra24 @benjaminhuo Looks like this doesn't work on amd64...

[...]
level=error msg="start Fluentd error" error="fork/exec /usr/local/bundle/bin/fluentd: no such file or directory"

Due to the fact that you re-tagged 1.15.3, this broke new pulls of the previously working image, as it now contains the bug, as well.

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

Successfully merging this pull request may close these issues.

bug: ARM image uses the incorrect path to the FluentD executable
4 participants