SpamAssassin as a Docker image. It runs
spamd on exposed port
constantly updates its ruleset.
docker run -d -p 783:783 babim/spamassassin
or linked (this is how I use it)
docker run -d --name spamassassin babim/spamassassin docker run -d --link spamassassin:spamassassin application-with-spamc-or-something
Configuration (environment variables)
None at the moment.
It has been a design decision to discard exporting the ruleset to a data
volume as it will be always be brought up-to-date (quite quickly) upon starting
a new container. Also currently there is no intention to have a custom config.
This is a poor man's
supervisord. It is my strong (but not so much challenged)
belief, that there shouldn't be yet another process manager (Docker has one,
CoreOS has one (with
The only thing this script does is watching its forked (background) processes
and as soon as one dies, it terminates all the others and exits with the code
of the first dying process.
- Make sure my little script above works in all circumstances. I know that when
-done cannot stop the process using