Mathies Svarrer-Lanthén

Yes that is correct. From my host OS `curl http://localhost:9200/` returned elasticsearch information and to confirm that the engine docker couldn't connect to elasticsearch i opened a shell inside that...

Yes that makes sense. By the way I will follow up on all the other issues i opened this Thursday. Thanks for the quick responses :)

I forgot to mention this, but it doesn't change anything about the way the issue should be fixed. For the workaround to work the elk stack will also have to...

My pull request #141 also includes a fix for this issue that is a little more future proof since with this chance it will become a problem again when kaitai...

It's because you need to build the kaitai docker image in the util folder locally. I updated the README intructions and included fixes for other problems you will run into...

I'm actually using docker, I just didn't change that in the pull request since I didn't want to change their default setting.

I still get almost the same error message: ``` 2018-12-06 11:07:43,242 - malice.get_signify - ERROR - sequence item 0: expected string, int found Traceback (most recent call last): File "/usr/sbin/malice/sig.py",...

Same result: ``` >> docker run -v `pwd`:/malware malice/kaspersky -t putty.exe time="2018-12-13T09:29:54Z" level=fatal msg="exit status 2" category=av path=/malware/putty.exe plugin=kaspersky ```