deepfence / deepfence/ThreatMapper
deepfence threatmapper not very durable on restarts - duplicate broker registration in kafka
- Dominant language
- TypeScript
- Stars
- 5.3k
- Forks
- 631
- PR merge metrics
- No merged PRs in 30d
Description
**Describe the bug**
deepfence threatmapper's compose mode doesn't handle reboots very gracefully.
**To Reproduce**
Steps to reproduce the behavior:
1. set up an EC2 with AWS linux, add docker and compose
2. run docker compose, set up a few things
3. operate a few reboots
4. kafka will fail to start.
**Expected behavior**
system should handle system restarts.
**Components/Services affected**
- [ ] UI/Frontend
- [x] API/Backend
- [ ] Agent
- [x] Deployment/YAMLs
- [ ] CI/CD Integration
- [ ] Other (specify)
**Additional context**
some instructions about AWS linux were incorrect for being temporary. that doesn't seem to be the final bug.
the edit should be in /etc/sysctl.conf to be permanent - https://www.elastic.co/guide/en/elasticsearch/reference/current/vm-max-map-count.html
Contributor guide
Assessment
This issue has not been assessed yet.