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

fails with read only mapped volumes #58

Closed
Shohou opened this issue Jan 8, 2019 · 3 comments
Closed

fails with read only mapped volumes #58

Shohou opened this issue Jan 8, 2019 · 3 comments

Comments

@Shohou
Copy link

Shohou commented Jan 8, 2019

docker-entrypoint.sh has this line:
chown --recursive "${GRAYLOG_USER}":"${GRAYLOG_GROUP}" "${GRAYLOG_HOME}/data"

It fails if I add files under data as read only volumes from the host. If I make them writable (which I don't like anyway) it changes owner and causes other troubles for me.

It would be nice to ignore this error when chown can't change owner. Please consider changing this line to
chown --recursive "${GRAYLOG_USER}":"${GRAYLOG_GROUP}" "${GRAYLOG_HOME}/data" || true

@jalogisch
Copy link
Contributor

The mapped volumes need to be read/write for the Graylog user as the journal is stored in this location.

We are using GitHub issues for tracking bugs in Graylog itself, but this doesn't look like one. Please post this issue to our discussion forum or join the #graylog channel on freenode IRC.

Thank you!

@Shohou
Copy link
Author

Shohou commented Jan 22, 2019

I guess journal is stored at some specific location under data directory, so not everything under data directory has to be writable. If I map as a volume some data/contentpacks/blabla.json does it need to be writable?

I don't ask to remove that line, I ask not to fail completely

@Shohou
Copy link
Author

Shohou commented Jan 22, 2019

or well, add another line which chowns data/journal separately and fail there if it is not writable

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

No branches or pull requests

2 participants