You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
this function checks paths exist, and chowns them to graylog:graylog if they aren't already owned by graylog:graylog
setup() {
# Create data directoriesfordin journal log plugin config contentpacks
do
dir=${GRAYLOG_HOME}/data/${d}
[[ -d"${dir}" ]] || mkdir -p "${dir}"if [[ "$(stat --format='%U:%G'$dir)"!='graylog:graylog' ]] && [[ -w"$dir" ]];then
chown -R graylog:graylog "$dir"||echo"Warning can not change owner to graylog:graylog"fidone
}
earlier in the script, you set a plugin directory with export GRAYLOG_PLUGIN_DIR=${GRAYLOG_HOME}/plugins-merged
should not for d in journal log plugin config contentpacks
be changed to for d in journal log ${GRAYLOG_PLUGIN_DIR} config contentpacks
It appears you are performing functions on a directory you don't use or care about. I wouldn't mind kicking in a PR, but before doing so I was curious if that was a conscious choice for backwards compatibility.
The text was updated successfully, but these errors were encountered:
https://github.com/Graylog2/graylog-docker/blob/5da05dfaae6f98929297acf1c19209a447d73ecf/docker-entrypoint.sh#L76C1-L87C2
this function checks paths exist, and chowns them to
graylog:graylog
if they aren't already owned bygraylog:graylog
earlier in the script, you set a plugin directory with
export GRAYLOG_PLUGIN_DIR=${GRAYLOG_HOME}/plugins-merged
should not
for d in journal log plugin config contentpacks
be changed to
for d in journal log ${GRAYLOG_PLUGIN_DIR} config contentpacks
It appears you are performing functions on a directory you don't use or care about. I wouldn't mind kicking in a PR, but before doing so I was curious if that was a conscious choice for backwards compatibility.
The text was updated successfully, but these errors were encountered: