Docker image does not start

[StianOvrevage]

Eager to try an alternative to the hard-to-operate ELK stack, but did not get very far:

$ docker run --name humio --rm -p 8080:8080 humio/humio
/run.sh: 10: /run.sh: [[: not found
/run.sh: 16: /run.sh: [[: not found
2018-11-28 21:17:21,935 CRIT Supervisor running as root (no user in config file)
2018-11-28 21:17:21,938 INFO supervisord started with pid 1
2018-11-28 21:17:22,941 INFO spawned: 'zookeeper' with pid 13
2018-11-28 21:17:22,942 INFO spawned: 'kafka' with pid 14
2018-11-28 21:17:22,943 INFO spawned: 'humio' with pid 15
2018-11-28 21:17:24,631 INFO success: zookeeper entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-11-28 21:17:24,631 INFO success: kafka entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-11-28 21:17:24,632 INFO success: humio entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

2018-11-28 21:17:55,050 INFO exited: humio (exit status 1; not expected)
2018-11-28 21:17:56,053 INFO spawned: 'humio' with pid 657
2018-11-28 21:17:57,548 INFO success: humio entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-11-28 21:18:27,669 INFO exited: humio (exit status 1; not expected)
2018-11-28 21:18:28,672 INFO spawned: 'humio' with pid 672
2018-11-28 21:18:30,148 INFO success: humio entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-11-28 21:19:08,808 INFO exited: humio (exit status 1; not expected)
2018-11-28 21:19:09,810 INFO spawned: 'humio' with pid 687
2018-11-28 21:19:11,290 INFO success: humio entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-11-28 21:19:47,829 INFO exited: humio (exit status 1; not expected)
2018-11-28 21:19:48,831 INFO spawned: 'humio' with pid 702
2018-11-28 21:19:50,308 INFO success: humio entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

Going to localhost:8080 results in ERR_EMPTY_RESPONSE in Chrome.

Docker for Windows:

$ docker -v
Docker version 18.06.1-ce, build e68fc7a

Also tried with --net=host as described in https://docs.humio.com/installation/docker/ but that gives Connection refused in browser.

[pmech]

hi @StianOvrevage,

Great that you are testing out Humio :). You can also join our Slack via community.humio.com if you wish.

The log shows that your Humio just enters a restart loop and never starts up correctly.

We don't support running on Windows and I'm unsure if there is any issues/differences between running docker on Windows, that might be it?

If you mount in the data dir -v some/dir/on/your/host:/data/, then you can find our debug log in some/dir/on/your/host/logs/humio-debug.log. I would expect that you see an exception there and that it might shed some light on the reason why it crashes at boot.

Regards,

-- Peter

[StianOvrevage]

Thanks for the swift reply!

I got the logs and apparently my laptop did not have enough memory. It would be nice to have those logs surfaced to stderr/stdout though :) I think you can configure supervisord to redirect logs for it's child processes to stderr/stdout.

There was also these two

/run.sh: 10: /run.sh: [[: not found
/run.sh: 16: /run.sh: [[: not found

That I thought might have something to do with it, and maybe they had something to do with being on Windows. But they show up both on Windows and Ubuntu.

Running it now on a bigger VM in the cloud on Ubuntu and it seems to be working great, thanks!

[pmech]

Great. Yes the [[: not found is annoying. I'll see if I can fix that.

I'll close this issue, but if you get more questions reach out to me (I'm part of the core Humio team) or join our Slack via community.humio.com.

Have a good day.