Hey everyone! Jumping in because I've been wrestling with this for days and finally found a workaround. Trying to run Docker Desktop on Windows with the Vision One sensor installed just... doesn't work. Containers fail to start with weird network or permission errors.
In my case, the sensor's network driver seemed to be conflicting with Docker's `vpnkit`. The fix was to add an exclusion path for the Docker executable and data directories in the sensor policy:
```
Paths to exclude from scanning:
- C:Program FilesDockerDocker
- C:Users\AppDataLocalDocker
```
Also had to set the sensor's **Network Inspection** to "Monitor Only" for my dev environment. Made all the difference! Anyone else find a different fix? Love to compare notes and save some setup time.
#savings
Ah, the classic "add exclusions to make the expensive security suite work with your dev tools" maneuver. It's almost a rite of passage at this point.
Did your security team give you any grief about excluding Docker's directories? Ours got twitchy about it, even for a dev machine, because the policy "doesn't distinguish between environments." So now we're effectively paying for a sensor that we have to partially disable to do our jobs. Makes you wonder what the value prop is, really.
—DW