diff --git a/images/docker-fail2ban/index.html b/images/docker-fail2ban/index.html index 6eca962da9..40e4417d48 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.
 
 
Info
 
Unless a parameter is flaged as 'optional', it is mandatory and a value must be provided.
 
  
---
 services:
   fail2ban:
     image: lscr.io/linuxserver/fail2ban:latest
@@ -63,7 +63,7 @@
   -v /path/to/vaultwarden/log:/remotelogs/vaultwarden:ro `#optional` \
   --restart unless-stopped \
   lscr.io/linuxserver/fail2ban:latest
-
 
Parameters
 
Containers are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate <external>:<internal> respectively. For example, -p 8080:80 would expose port 80 from inside the container to be accessible from the host's IP on port 8080 outside the container.
 
Ports (-p)
 
  
 Parameter Function 
   
   
  
 
Networking (--net)
 
  
 Parameter Function 
   
 --net=host Shares host networking with container. 
  
 
Environment Variables (-e)
 
  
 Env Function 
   
 PUID=1000 for UserID - see below for explanation 
 
 PGID=1000 for GroupID - see below for explanation 
 
 TZ=Etc/UTC specify a timezone to use, see this list. 
 
 VERBOSITY=-vv Set the container log verbosity. Valid options are -v, -vv, -vvv, -vvvv, or leaving the value blank or not setting the variable. 
  
 
Volume Mappings (-v)
 
  
 Volume Function 
   
 /config Persistent config files 
 
 /var/log:ro Host logs. Mounted as Read Only. 
 
 /remotelogs/airsonic:ro Optional path to airsonic log folder. Mounted as Read Only. 
 
 /remotelogs/apache2:ro Optional path to apache2 log folder. Mounted as Read Only. 
 
 /remotelogs/authelia:ro Optional path to authelia log folder. Mounted as Read Only. 
 
 /remotelogs/emby:ro Optional path to emby log folder. Mounted as Read Only. 
 
 /remotelogs/filebrowser:ro Optional path to filebrowser log folder. Mounted as Read Only. 
 
 /remotelogs/homeassistant:ro Optional path to homeassistant log folder. Mounted as Read Only. 
 
 /remotelogs/lighttpd:ro Optional path to lighttpd log folder. Mounted as Read Only. 
 
 /remotelogs/nextcloud:ro Optional path to nextcloud log folder. Mounted as Read Only. 
 
 /remotelogs/nginx:ro Optional path to nginx log folder. Mounted as Read Only. 
 
 /remotelogs/nzbget:ro Optional path to nzbget log folder. Mounted as Read Only. 
 
 /remotelogs/overseerr:ro Optional path to overseerr log folder. Mounted as Read Only. 
 
 /remotelogs/prowlarr:ro Optional path to prowlarr log folder. Mounted as Read Only. 
 
 /remotelogs/radarr:ro Optional path to radarr log folder. Mounted as Read Only. 
 
 /remotelogs/sabnzbd:ro Optional path to sabnzbd log folder. Mounted as Read Only. 
 
 /remotelogs/sonarr:ro Optional path to sonarr log folder. Mounted as Read Only. 
 
 /remotelogs/unificontroller:ro Optional path to unificontroller log folder. Mounted as Read Only. 
 
 /remotelogs/vaultwarden:ro Optional path to vaultwarden log folder. Mounted as Read Only. 
  
 
Miscellaneous Options
 
  
 Parameter Function 
   
   
  
 
Portainer notice
 
 
Warning
 
This image utilises cap_add or sysctl to work properly. This is not implemented properly in some versions of Portainer, thus this image may not work if deployed through Portainer.
 
 
Environment variables from files (Docker secrets)
 
You can set any environment variable from a file by using a special prepend FILE__.
 
As an example:
 
-e FILE__MYVAR=/run/secrets/mysecretvariable
+
 
Parameters
 
Containers are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate <external>:<internal> respectively. For example, -p 8080:80 would expose port 80 from inside the container to be accessible from the host's IP on port 8080 outside the container.
 
Ports (-p)
 
  
 Parameter Function 
   
   
  
 
Networking (--net)
 
  
 Parameter Function 
   
 --net=host Shares host networking with container. 
  
 
Environment Variables (-e)
 
  
 Env Function 
   
 PUID=1000 for UserID - see below for explanation 
 
 PGID=1000 for GroupID - see below for explanation 
 
 TZ=Etc/UTC specify a timezone to use, see this list. 
 
 VERBOSITY=-vv Set the container log verbosity. Valid options are -v, -vv, -vvv, -vvvv, or leaving the value blank or not setting the variable. 
  
 
Volume Mappings (-v)
 
  
 Volume Function 
   
 /config Persistent config files 
 
 /var/log:ro Host logs. Mounted as Read Only. 
 
 /remotelogs/airsonic:ro Optional path to airsonic log folder. Mounted as Read Only. 
 
 /remotelogs/apache2:ro Optional path to apache2 log folder. Mounted as Read Only. 
 
 /remotelogs/authelia:ro Optional path to authelia log folder. Mounted as Read Only. 
 
 /remotelogs/emby:ro Optional path to emby log folder. Mounted as Read Only. 
 
 /remotelogs/filebrowser:ro Optional path to filebrowser log folder. Mounted as Read Only. 
 
 /remotelogs/homeassistant:ro Optional path to homeassistant log folder. Mounted as Read Only. 
 
 /remotelogs/lighttpd:ro Optional path to lighttpd log folder. Mounted as Read Only. 
 
 /remotelogs/nextcloud:ro Optional path to nextcloud log folder. Mounted as Read Only. 
 
 /remotelogs/nginx:ro Optional path to nginx log folder. Mounted as Read Only. 
 
 /remotelogs/nzbget:ro Optional path to nzbget log folder. Mounted as Read Only. 
 
 /remotelogs/overseerr:ro Optional path to overseerr log folder. Mounted as Read Only. 
 
 /remotelogs/prowlarr:ro Optional path to prowlarr log folder. Mounted as Read Only. 
 
 /remotelogs/radarr:ro Optional path to radarr log folder. Mounted as Read Only. 
 
 /remotelogs/sabnzbd:ro Optional path to sabnzbd log folder. Mounted as Read Only. 
 
 /remotelogs/sonarr:ro Optional path to sonarr log folder. Mounted as Read Only. 
 
 /remotelogs/unificontroller:ro Optional path to unificontroller log folder. Mounted as Read Only. 
 
 /remotelogs/vaultwarden:ro Optional path to vaultwarden log folder. Mounted as Read Only. 
  
 
Miscellaneous Options
 
  
 Parameter Function 
   
 --cap-add=NET_ADMIN Required for fail2ban to be able to modify iptables rules. 
 
 --cap-add=NET_RAW Required for fail2ban to be able to bind to any interface & use RAW sockets. 
  
 
Portainer notice
 
 
Warning
 
This image utilises cap_add or sysctl to work properly. This is not implemented properly in some versions of Portainer, thus this image may not work if deployed through Portainer.
 
 
Environment variables from files (Docker secrets)
 
You can set any environment variable from a file by using a special prepend FILE__.
 
As an example:
 
-e FILE__MYVAR=/run/secrets/mysecretvariable
 
 
Will set the environment variable MYVAR based on the contents of the /run/secrets/mysecretvariable file.
 
Umask for running applications
 
For all of our images we provide the ability to override the default umask settings for services started within the containers using the optional -e UMASK=022 setting. Keep in mind umask is not chmod it subtracts from permissions based on it's value it does not add. Please read up here before asking for support.
 
User / Group Identifiers
 
When using volumes (-v flags), permissions issues can arise between the host OS and the container, we avoid this issue by allowing you to specify the user PUID and group PGID.
 
Ensure any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic.
 
In this instance PUID=1000 and PGID=1000, to find yours use id your_user as below:
 
id your_user
 
 
Example output:
 
uid=1000(your_user) gid=1000(your_user) groups=1000(your_user)
 
 
Docker Mods
 
Docker Mods Docker Universal Mods
 
We publish various Docker Mods to enable additional functionality within the containers. The list of Mods available for this image (if any) as well as universal mods that can be applied to any one of our images can be accessed via the dynamic badges above.
 
Support Info
 
     
  •  
    Shell access whilst the container is running:
     
    docker exec -it fail2ban /bin/bash
@@ -86,4 +86,4 @@
   --pull \
   -t lscr.io/linuxserver/fail2ban:latest .
 
     
    The ARM variants can be built on x86_64 hardware and vice versa using lscr.io/linuxserver/qemu-static
     
    docker run --rm --privileged lscr.io/linuxserver/qemu-static --reset
-
     
    Once registered you can define the dockerfile to use with -f Dockerfile.aarch64.
     
    Versions
     
       
    • 12.10.24: - Rebase to Alpine 3.20.
      •  
    • 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

  • 12.10.24: - Rebase to Alpine 3.20.
  • 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 diff --git a/images/docker-mullvad-browser/index.html b/images/docker-mullvad-browser/index.html index a801d4d12d..186c0e5214 100644 --- a/images/docker-mullvad-browser/index.html +++ b/images/docker-mullvad-browser/index.html @@ -17,7 +17,7 @@

PRoot Apps is included in all KasmVNC based containers, a list of linuxserver.io supported applications is located HERE.

Native Apps

It is possible to install extra packages during container start using universal-package-install. It might increase starting time significantly. PRoot is preferred.

  environment:
     - DOCKER_MODS=linuxserver/mods:universal-package-install
     - INSTALL_PACKAGES=libfuse2|git|gdb
-

Usage

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

---
+

Usage

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

Info

Unless a parameter is flaged as 'optional', it is mandatory and a value must be provided.

---
 services:
   mullvad-browser:
     image: lscr.io/linuxserver/mullvad-browser:latest
@@ -52,7 +52,7 @@
   --shm-size="1gb" \
   --restart unless-stopped \
   lscr.io/linuxserver/mullvad-browser:latest
-

Parameters

Containers are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate <external>:<internal> respectively. For example, -p 8080:80 would expose port 80 from inside the container to be accessible from the host's IP on port 8080 outside the container.

Ports (-p)

Parameter Function
3000 Mullvad Browser GUI.
3001 Mullvad Browser GUI HTTPS.

Environment Variables (-e)

Env Function
PUID=1000 for UserID - see below for explanation
PGID=1000 for GroupID - see below for explanation
TZ=Etc/UTC specify a timezone to use, see this list.
LOCAL_NET=192.168.0.0/16 If using a VPN, set this to your local LAN IP range using CIDR notation. Without it you will be unable to access the web interface. If you have multiple ranges or a complex LAN setup you will need to manage this yourself in the wg0.conf, see the App Setup section for details.

Volume Mappings (-v)

Volume Function
/config Users home directory in the container, stores local files and settings

Miscellaneous Options

Parameter Function
--shm-size= This is needed for any modern website to function like youtube.
--security-opt seccomp=unconfined For Docker Engine only, many modern gui apps need this to function on older hosts as syscalls are unknown to Docker.

Portainer notice

Warning

This image utilises cap_add or sysctl to work properly. This is not implemented properly in some versions of Portainer, thus this image may not work if deployed through Portainer.

Environment variables from files (Docker secrets)

You can set any environment variable from a file by using a special prepend FILE__.

As an example:

-e FILE__MYVAR=/run/secrets/mysecretvariable
+

Parameters

Containers are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate <external>:<internal> respectively. For example, -p 8080:80 would expose port 80 from inside the container to be accessible from the host's IP on port 8080 outside the container.

Ports (-p)

Parameter Function
3000:3000 Mullvad Browser GUI.
3001:3001 Mullvad Browser GUI HTTPS.

Environment Variables (-e)

Env Function
PUID=1000 for UserID - see below for explanation
PGID=1000 for GroupID - see below for explanation
TZ=Etc/UTC specify a timezone to use, see this list.
LOCAL_NET=192.168.0.0/16 If using a VPN, set this to your local LAN IP range using CIDR notation. Without it you will be unable to access the web interface. If you have multiple ranges or a complex LAN setup you will need to manage this yourself in the wg0.conf, see the App Setup section for details.

Volume Mappings (-v)

Volume Function
/config Users home directory in the container, stores local files and settings

Miscellaneous Options

Parameter Function
--shm-size= This is needed for any modern website to function like youtube.
--security-opt seccomp=unconfined For Docker Engine only, many modern gui apps need this to function on older hosts as syscalls are unknown to Docker.
--cap-add=NET_ADMIN Neccessary for Wireguard to create its VPN interface.

Portainer notice

Warning

This image utilises cap_add or sysctl to work properly. This is not implemented properly in some versions of Portainer, thus this image may not work if deployed through Portainer.

Environment variables from files (Docker secrets)

You can set any environment variable from a file by using a special prepend FILE__.

As an example:

-e FILE__MYVAR=/run/secrets/mysecretvariable

Will set the environment variable MYVAR based on the contents of the /run/secrets/mysecretvariable file.

Umask for running applications

For all of our images we provide the ability to override the default umask settings for services started within the containers using the optional -e UMASK=022 setting. Keep in mind umask is not chmod it subtracts from permissions based on it's value it does not add. Please read up here before asking for support.

User / Group Identifiers

When using volumes (-v flags), permissions issues can arise between the host OS and the container, we avoid this issue by allowing you to specify the user PUID and group PGID.

Ensure any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic.

In this instance PUID=1000 and PGID=1000, to find yours use id your_user as below:

id your_user

Example output:

uid=1000(your_user) gid=1000(your_user) groups=1000(your_user)

Docker Mods

Docker Mods Docker Universal Mods

We publish various Docker Mods to enable additional functionality within the containers. The list of Mods available for this image (if any) as well as universal mods that can be applied to any one of our images can be accessed via the dynamic badges above.

Support Info