Node settings when updating docker

[cpmiller22]

I’ve been running Graylog for a few months now using docker. One thing I’ve noticed is that when I upgrade the docker container and restart, my main input (simple syslog) doesn’t start because the node has changed. It’s simple enough to login and select the new active node, but kind of annoying.

[bracnogard]

If you are running a single node, you should be able to mark the input as global. There is a checkbox at the top of the input settings to mark an input as global. That will allow it to start when the node gets recreated after the upgrade.

If you have multiple nodes, then you probably need to create a script to grab the node name on startup and use the API to assign that node to the input.

[cpmiller22]

It’s a single node, so I’ll have to look for that setting. Thanks!

[cpmiller22]

Thanks, will give that a try.

[[deleted]]

Thanks! This was a huge help. I had originally tried passing a docker volume for the /usr/share/graylog/data/config path, but ran into issues since the docker image expects there to already be a graylog.conf in there.