-
-
Notifications
You must be signed in to change notification settings - Fork 78
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
docker-fail2ban:1.1.0 compatibility issue with Synology #164
Comments
Thanks for your report, can you give the output of the following commands please?:
I believe this is an issue linked to the update to Alpine 3.19. |
Can you try with |
Both command outputs were:
The error remains:
|
Unfortunately still an error…
|
Can you give full logs please similar to https://github.com/crazy-max/docker-fail2ban/actions/runs/9018916105/job/24780580461#step:8:10:
|
Sorry I'm confused... I forgot to repull the image... |
|
|
in my case is not working ---
services:
fail2ban:
image: crazymax/fail2ban:edge
container_name: fail2ban
cap_add:
- NET_ADMIN
- NET_RAW
network_mode: host
environment:
- PUID=1032
- PGID=100
- TZ=Europe/Madrid
volumes:
- /volume1/docker/fail2ban/data:/data
#- /var/log:/var/log:ro
- /volume1/docker/jellyfin/config/log:/remotelogs/jellyfin:ro
restart: unless-stopped Logs:
|
Support guidelines
I've found a bug and checked that ...
Description
Since crazymax/fail2ban:1.1.0, IPs are no longer banned.
Expected behaviour
IPs are banned without errors (last working version 1.0.2)
Actual behaviour
Steps to reproduce
Docker info
Docker Compose config
No response
Logs
Additional info
No response
The text was updated successfully, but these errors were encountered: