-
Notifications
You must be signed in to change notification settings - Fork 351
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
No more access to mounted /fluentd/logs folder #173
Comments
What the approach do other images take for such cases? |
For all other images we deploy there is no such issue |
Hmm... so ECS doesn't use https://github.com/fluent/fluentd-docker-image#change-running-user |
Do you use |
FLUENTD_UID does not help ( I've tried to set But I've tried to specify root user inside ECS container definition, this helps and write operations is allowed to the newly created logs folder. Tested on latest v1.4 version , not sure that it works on earlier versions. |
|
" Is there no other way than to give 777 permission on folder or adding fluent user on host and chown or building custom image?"
The reply is good for me. |
Are there any updates on this? Or workarounds or alternatives? I'm having the same issue. |
I run my fluentd as 'root' inside docker. |
This issue has been automatically marked as stale because it has been open 30 days with no activity. Remove stale label or comment or this issue will be closed in 7 days |
It seems that in the latest fluentd version there is now issue with mount of the host folder to /fluentd/logs
The issue happens on dynamically created EC2 instances in AWS. Docker deployment task definition has the mount point , like /var/log/fluentd/data to /fluentd/logs
During container deployment folder /var/log/fluentd/data is created on the host EC2, but after that there is no enough permissions to write into this folder:
To fix that we need manually execute something like chmod a+w /var/log/fluentd/data on the host then fluentd starts fine.
It seems that it is due to the latest changes in entrypoint.sh file.
Is it possible to fix it somehow?
The text was updated successfully, but these errors were encountered: