Install server and logging config into GRAYLOG_HOME/config #298
+40
−9
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We previously installed the configuration files into the GRAYLOG_HOME/data/config directory. We also documented that users should mount a volume to GRAYLOG_HOME/data to persist data.
When using a volume mount, Docker will copy existing files in GRAYLOG_HOME/data to the new volume. When using a bind mount (e.g., local directory), the directory doesn't include existing files, and the server refuses to start because it can't find the config files.
With the config files outside the data directory, this will no longer happen.
The entrypoint script will use existing config files in data/config to ensure existing setups with modified config files continue to work when updating to the new image.
See Graylog2/docker-compose#99 for details.
Also, adjust the list of directories that get created in GRAYLOG_HOME/data. We don't need the log and plugin directories.