dinkel / docker-spamassassin Goto Github PK

When attempting to shutdown the spamassessin container, it takes the timeout time until the container stops because the SIGTERM signal is not processed by all processes in the container. This causes the docker daemon to perform a forced shutdown after timeout passed, potentially causing data corruption, loss of time each time the container is stopped and other issues.

Expected: Graceful shoutdown.

How to reproduce: docker stop spamassessin

Further reading: https://medium.com/@gchudnov/trapping-signals-in-docker-containers-7a57fdda7d86

First thank you for crafting this image. We've been using it for a while without problems until recently, when it started to stop itself quite quickly:

$ docker run -ti --rm -p 783:783 dinkel/spamassassin
Oct 04 14:33:27.520495 check[11]: [ 2] [bootup] Logging initiated LogDebugLevel=3 to file:/dev/stderr
Oct  4 14:33:29.303 [11] info: spamd: server started on IO::Socket::IP [0.0.0.0]:783 (running version 3.4.1)
Oct  4 14:33:29.303 [11] info: spamd: server pid: 11
Oct  4 14:33:29.306 [11] info: spamd: server successfully spawned child process, pid 14
Oct  4 14:33:29.309 [11] info: spamd: server successfully spawned child process, pid 15
Oct  4 14:33:29.310 [11] info: prefork: child states: IS
Oct  4 14:33:29.310 [11] info: prefork: child states: II
  
/run.sh: line 25:     7 Terminated              /rule-update.sh
/run.sh: line 25:     8 Terminated              /spamd.sh

Hi, how should I configure spamassassin in the container for that: i have a server with two interfaces, one connected to router Internet, and the other connected to my personal LAN and I want to filter all emails from both server and client/clients.

Thanks!