# Suricata in docker doesn't block packets

**URL:** <https://forum.suricata.io/t/suricata-in-docker-doesnt-block-packets/3692>\
**Category:** Uncategorized\
**Tags:** docker, suricata\
**Created:** [July 12, 2023, 1:04pm UTC](https://forum.suricata.io/t/suricata-in-docker-doesnt-block-packets/3692 "2023-07-12T13:04:55Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![dmitriy](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.suricata.io/dmitriy/32/2196_2.png) [@dmitriy](https://forum.suricata.io/u/dmitriy)\
**Post date:** [July 12, 2023, 1:04pm UTC](https://forum.suricata.io/t/suricata-in-docker-doesnt-block-packets/3692/1 "2023-07-12T13:04:55Z")

</div>

Hello, team.  
I use dockerized Suricata 6.0.13 (jasonish/suricata:latest) and it doesn’t block traffic.  
Steps to reproduce.

1. Command to run container looks like:

```auto
docker run --name=suricata --rm -it --name=suricata --net=host \
    --cap-add=net_admin --cap-add=net_raw --cap-add=sys_nice \
    -v /opt/suricata/logs:/var/log/suricata \
    -v /opt/suricata/lib:/var/lib/suricata \
    -v /opt/suricata/etc:/etc/suricata \
    jasonish/suricata:latest -i eth0

```

1. Updating rules:

```auto
docker exec -it --user suricata suricata suricata-update -f

```

1. Modifying the rule 2100498 to drop packets:

```auto
drop ip any any -> any any (msg:"GPL ATTACK_RESPONSE id check returned root"; content:"uid=0|28|root|29|"; classtype:bad-unknown; sid:2100498; rev:7; metadata:created_at 2010_09_23, updated_at 2010_09_23;)

```

1. Reloading rules:

```auto
docker exec -it --user suricata suricata suricatasc -c reload-rules

```

1. Testing Invalid traffic:

```auto
curl --max-time 5 http://testmynids.org/uid/index.html

```

(no error recieved)

1. In fast.log I see ‘wDrop’ record:

```auto
07/12/2023-12:25:38.959068 [**] [1:2013028:7] ET POLICY curl User-Agent Outbound [**] [Classification: Attempted Information Leak] [Priority: 2] {TCP} 192.168.88.122:44172 -> 52.XX.XX.69:80
07/12/2023-12:25:39.012621 [wDrop] [**] [1:2100498:7] GPL ATTACK_RESPONSE id check returned root [**] [Classification: Potentially Bad Traffic] [Priority: 2] {TCP} 52.XX.XX.69:80 -> 192.168.88.1
22:44172

```

but packets was not blocked.

Please help me, what I do wrong?

---

<div class="post-metadata">

**Author:** ![vjulien](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.suricata.io/vjulien/32/4_2.png) [@vjulien](https://forum.suricata.io/u/vjulien)\
**Post date:** [July 12, 2023, 7:16pm UTC](https://forum.suricata.io/t/suricata-in-docker-doesnt-block-packets/3692/2 "2023-07-12T19:16:59Z")

</div>

Looks like suricata is running in IDS mode, not in IPS mode. So no blocking occurs.

See:  
[https://docs.suricata.io/en/latest/setting-up-ipsinline-for-linux.html](https://docs.suricata.io/en/latest/setting-up-ipsinline-for-linux.html)

---

<div class="post-metadata">

**Author:** ![dmitriy](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.suricata.io/dmitriy/32/2196_2.png) [@dmitriy](https://forum.suricata.io/u/dmitriy)\
**Post date:** [July 13, 2023, 7:04am UTC](https://forum.suricata.io/t/suricata-in-docker-doesnt-block-packets/3692/3 "2023-07-13T07:04:53Z")

</div>

@vjulien Thanks for your opinion. Are you familiar with this product jasonish/suricata? I’m not sure it has a choice of operating mode.

@ish Maybe you can help?

---

<div class="post-metadata">

**Author:** ![Andreas\_Herz](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.suricata.io/andreas_herz/32/52_2.png) [@Andreas\_Herz](https://forum.suricata.io/u/Andreas_Herz)\
**Post date:** [July 31, 2023, 8:13pm UTC](https://forum.suricata.io/t/suricata-in-docker-doesnt-block-packets/3692/4 "2023-07-31T20:13:55Z")

</div>

First of all, which type of IPS mode do you plan to use?  
You can also pass dedicated run commands and should also build your suricata.yaml accordingly.
