Fail2Ban crash

[Gandulf78]

Behaviour

Steps to reproduce this issue

Just try to run fail2ban on Docker with:

docker run -d --name fail2ban --restart always
--network host
--cap-add NET_ADMIN
--cap-add NET_RAW
-v /mnt/HD/HD_a2/user/fail2ban/data:/data
-v /var/log:/var/log:ro
crazymax/fail2ban:latest

Sometimes encountering "ERRO[0024] error waiting for container: context canceled"

Expected behaviour

Tell me what should happen

Actual behaviour

Tell me what happens instead

Configuration

• Docker version (type docker --version) :

Client: Docker Engine - Community
Version: 19.03.8
API version: 1.40
Go version: go1.12.17
Git commit: afacb8b
Built: Wed Mar 11 01:23:36 2020
OS/Arch: linux/arm
Experimental: false

Server: Docker Engine - Community
Engine:
Version: 19.03.8
API version: 1.40 (minimum version 1.12)
Go version: go1.12.17
Git commit: afacb8b
Built: Wed Mar 11 01:45:06 2020
OS/Arch: linux/arm
Experimental: false
containerd:
Version: v1.2.13
GitCommit: 7ad184331fa3e55e52b890ea95e65ba581ae3429
runc:
Version: 1.0.0-rc10
GitCommit: dc9208a3303feef5b3839f4323d9beb36df0a9dd
docker-init:
Version: 0.18.0
GitCommit: fec3683

• Docker compose version if applicable (type docker-compose --version) :
• Platform (Debian 9, Ubuntu 18.04, ...) :
• System info (type uname -a) :

Linux MyCloudEX2Ultra 4.14.22-armada-18.09.3 #1 SMP Mon Dec 21 02:42:49 UTC 2020 ga-18.09.3 Build-24 armv7l GNU/Linux

• Include all necessary configuration files : docker-compose.yml, .env, ...

docker run -d --name fail2ban --restart always
--network host
--cap-add NET_ADMIN
--cap-add NET_RAW
-v /mnt/HD/HD_a2/user/fail2ban/data:/data
-v /var/log:/var/log:ro
crazymax/fail2ban:latest

Docker info

> Output of command `docker info`

Client:
 Debug Mode: false

Server:
 Containers: 8
  Running: 7
  Paused: 0
  Stopped: 1
 Images: 10
 Server Version: 19.03.8
 Storage Driver: vfs
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 7ad184331fa3e55e52b890ea95e65ba581ae3429
 runc version: dc9208a3303feef5b3839f4323d9beb36df0a9dd
 init version: fec3683
 Security Options:
  seccomp
   Profile: default
 Kernel Version: 4.14.22-armada-18.09.3
 OSType: linux
 Architecture: armv7l
 CPUs: 2
 Total Memory: 1012MiB
 Name: MyCloudEX2Ultra
 ID: H346:NCBN:2ZS3:2ED2:4DOL:IMOM:U5DI:EPA4:OMLD:MT4M:N5EM:LR2Z
 Docker Root Dir: /mnt/HD/HD_a2/Nas_Prog/_docker
 Debug Mode: false
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false
 Product License: Community Engine

Logs

> Container logs (set LOG_LEVEL to debug if applicable)

Setting timezone to UTC...
Setting SSMTP configuration...
WARNING: SSMTP_HOST must be defined if you want fail2ban to send emails
Initializing files and folders...
Setting Fail2ban configuration...
Checking for custom actions in /data/action.d...
Checking for custom filters in /data/filter.d...
Fatal Python error: init_interp_main: can't initialize time
Python runtime state: core initialized
PermissionError: [Errno 1] Operation not permitted

Current thread 0xb6832390 (most recent call first):

[Gandulf78]

Problem with time64 solved using following guidance

https://wiki.alpinelinux.org/w/index.php?title=Release_Notes_for_Alpine_3.13.0&oldid=19609#time64_requirements