Skip to content
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

symlink_path is absolute, so link is broken when accessed from host #50

Closed
edrex opened this issue Aug 30, 2016 · 4 comments
Closed

symlink_path is absolute, so link is broken when accessed from host #50

edrex opened this issue Aug 30, 2016 · 4 comments
Labels
stale Inactive and will be closed automatically

Comments

@edrex
Copy link

edrex commented Aug 30, 2016

When following the instructions in the readme, the symlink created by fluentd via symlink_path /fluentd/log/docker.log is broken when read from the host. If the symlink were relative it would work. It looks like this would require a change upstream, but reporting here since it's a problem primarily when using the docker image.

@kkujawinski
Copy link

There is workaround for this issue:

  1. You mount fluent home directory:

    docker run -d -p 24224:24224 -v /data:/home/fluent fluent/fluentd
    
  2. Define relative path for path and symlink_path:

    path ${tag}.*.log
    symlink_path "${tag}.log"
    

@nico1106
Copy link

nico1106 commented Jun 4, 2019

Home Directory doesn't work. The trick is that you have to set the "working directory" during the container startup with "-w". Then your files will be created in that directory.
You can mount this directory as well.

Copy link

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

@github-actions github-actions bot added the stale Inactive and will be closed automatically label Aug 30, 2024
Copy link

github-actions bot commented Sep 6, 2024

This issue was automatically closed because of stale in 7 days

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Inactive and will be closed automatically
Projects
None yet
Development

No branches or pull requests

3 participants