diff --git a/images/docker-fail2ban/index.html b/images/docker-fail2ban/index.html index e9a73d6a78..09fed108fe 100644 --- a/images/docker-fail2ban/index.html +++ b/images/docker-fail2ban/index.html @@ -1,4 +1,4 @@ - fail2ban - LinuxServer.io
Skip to content

linuxserver/fail2ban

Scarf.io pulls GitHub Stars GitHub Release GitHub Package Repository GitLab Container Registry Quay.io Docker Pulls Docker Stars Jenkins Build LSIO CI

Fail2ban is a daemon to ban hosts that cause multiple authentication errors.

fail2ban

Supported Architectures

We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here.

Simply pulling lscr.io/linuxserver/fail2ban:latest should retrieve the correct image for your arch, but you can also pull specific arch images via tags.

The architectures supported by this image are:

Architecture Available Tag
x86-64 ✅ amd64-<version tag>
arm64 ✅ arm64v8-<version tag>
armhf ❌

Application Setup

This container is designed to allow fail2ban to function at the host level, as well as at the docker container level. If you are running applications on the host, you will need to set the chain to INPUT in the jail for that application.

Configuration Files

On first run, the container will create a number of folders and files in /config. The default configurations for fail2ban are all disabled by default.

Please refer to the Configuration README, which can be viewed in our repository, or in your config folder at /config/fail2ban/README.md.

Remote Logs

All jails require the ability to read the application log files. We recommend mounting each application's log folder as a volume to the container (illustrated by the optional volumes in our documentation). Mounting individual log files can cause issues and is not recommended.

The /remotelogs path is designed to act as a parent for all log files you would like fail2ban to be able to use. Each log file should be mounted in a subfolder underneath /remotelogs, ex: - /remotelogs/nginx/ would mount a folder containing the nginx logs to the container

Usage

To help you get started creating a container from this image you can either use docker-compose or the docker cli.

---
+ fail2ban - LinuxServer.io      
 
 
  
 
  
 
 
 
 
  
 
 
 
 
 
  
 
 
 
 
   
linuxserver/fail2ban
 
Scarf.io pulls GitHub Stars GitHub Release GitHub Package Repository GitLab Container Registry Quay.io Docker Pulls Docker Stars Jenkins Build LSIO CI
 
Fail2ban is a daemon to ban hosts that cause multiple authentication errors.
 
fail2ban
 
Supported Architectures
 
We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here.
 
Simply pulling lscr.io/linuxserver/fail2ban:latest should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
 
The architectures supported by this image are:
 
  
 Architecture Available Tag 
   
 x86-64 ✅ amd64-<version tag> 
 
 arm64 ✅ arm64v8-<version tag> 
 
 armhf ❌  
  
 
Application Setup
 
This container is designed to allow fail2ban to function at the host level, as well as at the docker container level. If you are running applications on the host, you will need to set the chain to INPUT in the jail for that application.
 
Configuration Files
 
On first run, the container will create a number of folders and files in /config. The default configurations for fail2ban are all disabled by default.
 
Please refer to the Configuration README, which can be viewed in our repository, or in your config folder at /config/fail2ban/README.md.
 
Remote Logs
 
All jails require the ability to read the application log files. We recommend mounting each application's log folder as a volume to the container (illustrated by the optional volumes in our documentation). Mounting individual log files can cause issues and is not recommended.
 
The /remotelogs path is designed to act as a parent for all log files you would like fail2ban to be able to use. Each log file should be mounted in a subfolder underneath /remotelogs, ex: - /remotelogs/nginx/ would mount a folder containing the nginx logs to the container
 
Usage
 
To help you get started creating a container from this image you can either use docker-compose or the docker cli.
  
---
 services:
   fail2ban:
     image: lscr.io/linuxserver/fail2ban:latest
@@ -86,4 +86,4 @@
   --pull \
   -t lscr.io/linuxserver/fail2ban:latest .
 
 
The ARM variants can be built on x86_64 hardware using multiarch/qemu-user-static
 
docker run --rm --privileged multiarch/qemu-user-static:register --reset
-
 
Once registered you can define the dockerfile to use with -f Dockerfile.aarch64.
 
Versions
 
     
  • 05.03.24: - Rebase to Alpine 3.19.
    •  
  • 01.06.23: - Add optional VERBOSITY environment variable, allowing users to set the container log verbosity.
    •  
  • 25.05.23: - Rebase to Alpine 3.18, deprecate armhf.
    •  
  • 15.12.22: - Replace unmaintained ssmtp with msmtp.
    •  
  • 15.12.22: - Rebase to Alpine 3.17, Add ssmtp and whois packages. Symlink config to allow live reloading.
    •  
  • 25.08.22: - Update README to clarify remote log information.
    •  
  • 09.08.22: - Initial Release.
    •  
  
 
  
  
  
 
 
 
      
\ No newline at end of file
+

Once registered you can define the dockerfile to use with -f Dockerfile.aarch64.

Versions

  • 05.03.24: - Rebase to Alpine 3.19.
  • 01.06.23: - Add optional VERBOSITY environment variable, allowing users to set the container log verbosity.
  • 25.05.23: - Rebase to Alpine 3.18, deprecate armhf.
  • 15.12.22: - Replace unmaintained ssmtp with msmtp.
  • 15.12.22: - Rebase to Alpine 3.17, Add ssmtp and whois packages. Symlink config to allow live reloading.
  • 25.08.22: - Update README to clarify remote log information.
  • 09.08.22: - Initial Release.
\ No newline at end of file