-
Notifications
You must be signed in to change notification settings - Fork 980
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
All recent elasticsearch-tagged builds are broken #164
Comments
I think the reason for this is this 1be6199#diff-9523e3b7e53f948647db88acc163b05b Is there any particular reason why this project is not using releases? Github help |
I build manually that commit and deployed on my K8s cluster but keeps failing... I had to go back to 30cc62d to make it work |
head /fluentd/entrypoint.sh
|
The latest builds has major mistake and the entrypoint.sh modify /bin/bash to /usr/bin/dumb-init, but the file is not exist |
It is because the base image |
I see. So updating base image to latest v0.12 seems to resolve the problem. |
@carlosjgp @repeatedly Thanks for the quick turnaround. Much appreciated. However, I'm now getting the classic user issue:
|
I am getting this error as well. I am using the helm chart for Any suggestions to get this stable and working would be appreciated. |
Issue is resolved by the patch. So close this issue. |
@repeatedly I appreciate that you're trying to close things that are fixed, but did you see #164 (comment)? |
@teotwaki set env variable FLUENT_UID to "0". |
@marulm that does work, but the initial value has to be |
Hi @teotwaki, is this still a problem? If it is, can you create a gist with your K8s deployment? Make sure you are mounting '/var/log' with write privileges. |
Getting the same error - using FLUENT_UIDenv:
|
@Tikam02 |
Hi,
I might be doing something wrong, but I want to double check with the project first. I was using
fluent/fluentd-kubernetes-daemonset:elasticsearch
in my cluster very happilly, and then when the cluster autoscaled today (and only today) fluentd failed to start. The logs only showed this one line:I switched to a few other tags to try and cirumvent the issue, but encountered the same problem on all the following tags:
v0.12-alpine-elasticsearch
v0.12.33-elasticsearch
v0.12-elasticsearch
stable-elasticsearch
elasticsearch
A version that I found that worked was
v1.2-debian-elasticsearch
. My definition of "found" in this case being "booted and sent logs to elasticsearch".The text was updated successfully, but these errors were encountered: