Docker container cannot restart services after being stopped about graylog2-images

[mariussturm]

Awesome, thanks for the detailed report. Will take a look!

[mariussturm]

The only useful solution I can see here is to ditch the bridged network completely. When I start the container like this: docker run --net=host -t graylog2/allinone the stop/start cycle works.

[dfch]

Hi Marius, thanks for your suggestion. However, this would only be something for use in a test environment (as the whole container is completely connected with the host). I had a look at the config of elasticsearch and graylog2 files and it seems that upon first boot the ip address is registered (rather than the hostname). It might be a better approach to register the host name in the config files (and update the hosts file upon every restart). Thanks anyway! Ronald

[mariussturm]

It would also be possible to let all services listen on localhost in that way no reconfiguration is needed. But this will break the ability to split services into single containers: https://github.com/Graylog2/graylog2-images/tree/master/docker#multi-container-setup which is a main idea of Docker, small services in small containers.

[mariussturm]

The restart issue should be fixed in the latest container, we connect now all services against localhost. No need to change anything after a container restart.