Closed jfillman closed 6 years ago
This is also happening to me. I can run bash on the box as the same user (root) and cat all the logs. But I am also getting the 'log unreadable' error. Any chance we can get some help? It's really disappointing that there's been no feedback on this issue for 28 days.
Hi, I had same problem and solved when I delete --lod-driver=journald in docker.conf file. If you check the folder /var/log/containers it would be empty and that's why you receive this error message.
Could you try this?
securityContext:
readOnlyRootFilesystem: true
Considering this ticket as solved due to previous answers.
@jfillman did you solved it? and how solved? i have the same issue.
I have same problem . flunt-bit output log
[2019/10/11 10:43:59] [error] [in_tail] read error, check permissions: /home/docker/containers/*/*.log
check the directory permissions 0755 is ok
same issue
[2020/02/26 03:53:13] [error] [in_tail] read error, check permissions: /data/ratelimit-logs/gateway_2.log [2020/02/26 03:53:13] [error] [in_tail] read error, check permissions: /data/ratelimit-logs/gateway_ratelimit.log
This is not fluent-bit daemonset repository. If you have a problem with fluent-bit, post it to correct place.
I had this problem and it was due to SELinux profiles
@jpiper how did you solve it?
I just set SELinux to permissive. Not really a solution, just a workaround
@jpiper and @perezmark
Updating the containers
securityContext and adding the spc_t
SELinux policy to the fluentd
DaemonSet worked for me:
Like so:
containers:
- name: fluentd
securityContext:
runAsNonRoot: false
runAsUser: 0
seLinuxOptions:
type: spc_t
This may be a better solution than just turning off SELinux on the all the nodes.
This issue must have come up before so apologies for not finding it.
My fluentd containers are now run as user '1000' and so don't have read access to /var/lib/docker/containers which is owned by root and has 0700 perms.
I get the log error mesg: