[Bro] problem with bro in container

erik clark philosnef at gmail.com
Thu Jun 1 06:53:44 PDT 2017

When I run my container like so:

docker run -v /data:/data --name bro -it --net=host bro /opt/bro/bin/broctl

it seems to fail immediately. There is no useful information in the logs in
spool or current.

When I run it as

docker run -v /data:/data --name bro -it --net=host bro /bin/bash

and start broctl deploy manually, it works fine and my logs are mapped back
like they should be. Why is bro bailing like this? I've confirmed that
/opt/bro/spool is mapped to /data/bro/spool in broctl.cfg, but even when I
leave it mapped back to /opt/bro/spool, it still fails to stay up when
deployed with

/opt/bro/bin/broctl deploy

Please advise
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/bro/attachments/20170601/38eb7190/attachment.html 

More information about the Bro mailing list