# Deploying Bro Cluster using Docker container technology **URL:** \ **Category:** Zeek\ **Created:** [August 25, 2015, 2:05am UTC](https://community.zeek.org/t/deploying-bro-cluster-using-docker-container-technology/3789 "2015-08-25T02:05:08Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Laaziz\_Lahlou](https://avatars.discourse-cdn.com/v4/letter/l/bb73d2/32.png) [@Laaziz\_Lahlou](https://community.zeek.org/u/Laaziz_Lahlou)\ **Post date:** [August 25, 2015, 2:05am UTC](https://community.zeek.org/t/deploying-bro-cluster-using-docker-container-technology/3789/1 "2015-08-25T02:05:08Z")
Hi guys, I’m trying to deploy Bro Cluster using Docker container technology for my master’s research project on Network Function Virtualization. The objective is to use pf\_send and replay a pcap file obtained from [http://download.netresec.com/pcap/smia-2011/SMIA\_2011-10-12\_07%253A41%253A40\_CEST\_606532000\_file2.pcap.](http://download.netresec.com/pcap/smia-2011/SMIA_2011-10-12_07%253A41%253A40_CEST_606532000_file2.pcap) I configured PF\_RING and created 5 containers as workers. I guess here I’m violating what is cited in : [https://www.bro.org/sphinx/cluster/index.html](https://www.bro.org/sphinx/cluster/index.html) The PF\_RING software for Linux has a “clustering” feature which will do flow-based load balancing across a number of processes that are sniffing the same interface". What I mean here is each container has it’s own interface and the workers are not listening on the same interface,so am I right or should I deploy the whole Bro Cluster just on one container ? I will appreciate any comment and guidance. Best regards. Aziz **MSc Sécurité, Réseaux et e-Santé** **Université Paris Descartes** ---
**Author:** ![system](https://canada1.discourse-cdn.com/flex011/uploads/zeek/original/1X/f09d732bc2cc7c7cc7e35db67cf4e1d5233ce7a7.png) [@system](https://community.zeek.org/u/system)\ **Post date:** [May 6, 2022, 3:43pm UTC](https://community.zeek.org/t/deploying-bro-cluster-using-docker-container-technology/3789/2 "2022-05-06T15:43:00Z")
Closed on May 6, 2022, 3:43pm UTC