-
-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RancherOS support? #25
Comments
I was able to get it working for sshd on RancherOS using the following version: '3'
services:
fail2ban:
image: crazymax/fail2ban
restart: always
network_mode: host
cap_add:
- NET_ADMIN
- NET_RAW
environment:
F2B_LOG_LEVEL: DEBUG
volumes:
- ./data:/data
- /var/log:/var/log:ro The contents of
After IPs are banned, you should see some data when running
One thing I do find odd are DEBUG logs like these. It would be interesting to know if this is resolvable or if it has any negative impact.
|
Hi @divThis, RancherOS is being deprecated and there won't be any further development according to Rancher, so I would recommend against using it. :) |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Hi! This is not really a bug report so I hope it's OK if I ask a question here. I am looking to use RancherOS both for the Rancher management platform and for my Kubernetes hosts. Since everything in RancherOS runs as a container - including system services - I was looking for how to use fail2ban as a container, and found this repo. Has anyone tried docker-fail2ban with RancherOS? Does it work?
Thanks a lot in advance for your help!
The text was updated successfully, but these errors were encountered: